| 3 | Approval of the Agenda | |
|---|---|---|
| R3-200002 | RAN3#107-e Meeting Agenda | Chairman (Ericsson) |
| 4 | Approval of the minutes from previous meetings | |
| R3-200077 | RAN3#106 Meeting report | ETSI - MCC |
| 5 | Documents for immediate consideration | |
| R3-200134 | Guidelines for RAN3 #107-e as Electronic Meeting | RAN3 Chairman, RAN3 Vice-Chairs |
| R3-200195 | Guidelines for RAN3 #107-e as Electronic Meeting | RAN3 Chairman, RAN3 Vice-Chairs |
| R3-201208 | List of E-mail Discussions | Chairman (Ericsson) |
| 7.1 | RAN3 Contribution Quota | |
| R3-200133 | Introduction of Tdoc Quotas | RAN3 Chairman, RAN3 Vice-Chairs |
| 7.2 | Port Assignment Request for W1 Interface – Coordination with IANA | |
| R3-200336 | Discussion on Port Assignment for W1 interface | ZTE Corporation |
| R3-200463 | Discussion on IANA Port Assignment | Huawei |
| R3-201089 | Discussion on IANA port number allocation request for W1 interface | China Unicom |
| R3-201209 | DNS-based Service Discovery for W1AP | Orange |
| R3-201210 | Discussion on W1 aspects | Orange |
| R3-201212 | Summary of offline discussion on Port Assignment for W1 interface | Huawei |
| R3-201213 | LS on Port Assignment for W1 interface | Huawei |
| 8.1 | New Incoming LSs | |
| R3-200078 | General Status of Work | Broadband_Forum |
| R3-200079 | LS on agreements related to NR Positioning | 3GPP RAN1 |
| R3-200080 | Reply LS on PRACH configuration conflict detection | 3GPP RAN1 |
| R3-200081 | LS on updated Rel-16 LTE and NR parameter lists | 3GPP RAN1 |
| R3-200082 | Reply LS on uplink TDM pattern for LTE DAPS based enhanced make-before-break HO | 3GPP RAN1 |
| R3-200083 | Reply LS on QoE Measurement Collection | 3GPP RAN2 |
| R3-200084 | LS on Conditional PSCell addition/change | 3GPP RAN2 |
| R3-200085 | Reply LS on NID structure and length | 3GPP RAN2 |
| R3-200086 | Reply LS on Sending CAG ID in NAS layer | 3GPP RAN2 |
| R3-200087 | Reply LS on Mobile-terminated Early Data Transmission | 3GPP RAN2 |
| R3-200088 | LS on UE identifier for UP CIoT 5GS Optimisation | 3GPP RAN2 |
| R3-200089 | Reply LS on assistance indication for WUS | 3GPP RAN2 |
| R3-200090 | Reply LS on resource coordination between NG-RAN nodes for NR V2X sidelink communication | 3GPP RAN2 |
| R3-200091 | LS on dependencies on AS design for mobility management aspects of NTN in 5GS | 3GPP RAN2 |
| R3-200092 | Reply LS on CSI-RS configuration transfer | 3GPP RAN2 |
| R3-200093 | LS on updates for TS 36.300 and TS 38.300 | 3GPP RAN2 |
| R3-200094 | LS on Network Coordination for UL PDCP Duplication | 3GPP RAN2 |
| R3-200095 | LS on F1AP over LTE leg signalling for IAB | 3GPP RAN2 |
| R3-200096 | LS on EN-DC related MDT configuration details | 3GPP RAN2 |
| R3-200097 | LS on RACH report and RLF report. | 3GPP RAN2 |
| R3-200098 | LS on trace related configurations for NR MDT | 3GPP RAN2 |
| R3-200099 | LS on inter-RAT HO from SA to EN-DC | 3GPP RAN2 |
| R3-200100 | LS on LS on system level design assumptions for satellite in 5GS | 3GPP RAN2 |
| R3-200101 | LS on handover without SN configuration query | 3GPP RAN2 |
| R3-200102 | Reply LS on extended NAS timers for CE in 5GS | 3GPP RAN2 |
| R3-200103 | Response LS on Reference Point for Timing Related Measurements in FR2 | 3GPP RAN4 |
| R3-200104 | LS on Local NR positioning in NG-RAN | 3GPP TSG RAN |
| R3-200105 | Reply LS on UAC for NB-IOT | 3GPP SA1 |
| R3-200106 | Reply LS on NPN clarifications | 3GPP SA1 |
| R3-200107 | LS OUT on Location of UEs and associated key issues | 3GPP SA2 |
| R3-200108 | LS on RAN sharing for NPNs | 3GPP SA2 |
| R3-200109 | Reply LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | 3GPP SA2 |
| R3-200110 | Reply LS on Rel-16 NB-IoT enhancements | 3GPP SA2 |
| R3-200111 | LS on the support for ECN in 5GS | 3GPP SA2 |
| R3-200112 | LS reply on NPN network sharing | 3GPP SA2 |
| R3-200113 | LS reply on CAG definition | 3GPP SA2 |
| R3-200114 | Reply LS on assistance indication for WUS | 3GPP SA2 |
| R3-200115 | LS on Sending CAG ID | 3GPP SA2 |
| R3-200116 | Forwarding LS on definition of GLI | 3GPP SA2 |
| R3-200117 | Reply LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | 3GPP SA2 |
| R3-200118 | LS on 5GC assisted cell selection for accessing network slice | 3GPP SA2 |
| R3-200119 | Reply LS on assistance indication for WUS | 3GPP SA2 |
| R3-200120 | Reply LS to LS on AS key derivation for conditional handover (R2-1911565) | 3GPP SA3 |
| R3-200121 | Reply LS to SA2 on 5G-S-TMSI Truncation Procedure | 3GPP SA3 |
| R3-200122 | Reply LS on Handling of UE radio network capabilities in 4G and 5G | 3GPP SA3 |
| R3-200123 | Reply LS on Sending CAG ID in NAS layer | 3GPP SA3 |
| R3-200124 | Response LS on the ""LS OUT on Location of UEs and associated key issues"" | 3GPP SA3Li |
| R3-200125 | Reply on QoE Measurement Collection | 3GPP SA4 |
| R3-200126 | Reply LS on Support for ECN in 5GS | 3GPP SA4 |
| R3-200127 | Reply LS to LS to SA5 and SA2 on 5G Cell ID(s) in the 3GPP SA5 billing system, related to Retained Data regulations | 3GPP SA5 |
| R3-200128 | LS on Reply on QoE Measurement Collection | 3GPP SA5 |
| R3-200129 | Reply on radio resource management policy | 3GPP SA5 |
| R3-200130 | LS on NPN network sharing | 3GPP SA5 |
| R3-200131 | LS on CAG definition | 3GPP SA5 |
| R3-200132 | LS on analysis of GSMA GST attributes | 3GPP SA5 |
| R3-200136 | SA to EN DC handover and direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom |
| R3-200137 | SA to EN DC direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom |
| R3-200172 | Consideration on UE specific DRX in EPS and 5GS | Huawei |
| R3-200173 | [DRAFT] Reply LS on Rel-16 NB-IoT enhancements | Huawei |
| R3-200177 | Review of RAN2 running CRs for NB-IoT and eMTC | Huawei |
| R3-200178 | RAN3 inputs to RAN2 NB-IoT 36.300 CR | Huawei |
| R3-200179 | RAN3 inputs to RAN2 eMTC 36.300 CR | Huawei |
| R3-200180 | [DRAFT] Reply LS on updates for TS 36.300 and TS 38.300 | Huawei |
| R3-200300 | General status of WWC work | Broadband_Forum |
| R3-200359 | Inter-MN Handover without SN configuration Information | NEC |
| R3-200360 | Inter-MN Handover without SN configuration Information | NEC |
| R3-200361 | Inter-MN Handover without SN configuration Information | NEC |
| R3-200362 | draft response to SA2 LS on Location of UEs and associated key issues | THALES |
| R3-200427 | Further Consideration on CSI-RS Configuration Transfer | China Telecom, ZTE, CATT |
| R3-200456 | SA to ENDC handover with shared SgNB/gNB | CATT,Nokia, Nokia Shanghai Bell,Samsung, China Telecom |
| R3-200477 | CR to 36.423 on the support of CSI-RS based mobility | China Telecom, ZTE, CATT |
| R3-200478 | CR to 38.423 on the support of CSI-RS based mobility | China Telecom, ZTE, CATT |
| R3-200481 | CR to 38.473 on the support of CSI-RS based mobility | China Telecom Corporation Ltd. |
| R3-200578 | SA to EN DC direct forwarding with shared SgNB/gNB | Samsung, Nokia, Nokia Shanghai Bell, CATT, China Telecom |
| R3-200675 | Unsecured UE capability handling | NTT DOCOMO INC. |
| R3-200676 | CR for NG on unsecured UE capability handling | NTT DOCOMO INC. |
| R3-200678 | CR for S1 on unsecured UE capability handling | NTT DOCOMO INC. |
| R3-200685 | Discussion on handover without SN configuration query | Huawei |
| R3-200686 | Provision of used DRB IDs | Huawei |
| R3-200687 | Provision of used DRB IDs | Huawei |
| R3-200688 | Provision of used DRB IDs | Huawei |
| R3-200689 | Provision of used DRB IDs | Huawei |
| R3-200690 | [DRAFT] Reply LS on handover without SN configuration query | Huawei |
| R3-200728 | Provision of used DRB IDs | Huawei |
| R3-200729 | Provision of used DRB IDs | Huawei |
| R3-200730 | Provision of used DRB IDs | Huawei |
| R3-200731 | Provision of used DRB IDs | Huawei |
| R3-200771 | draft Reply LS on inter-RAT HO from SA to EN-DC | China Telecom Corporation Ltd. |
| R3-201004 | Discussion on RAN3 review to RAN2 stage 2 CRs | Ericsson |
| R3-201005 | RAN3 TP to R2-1916361 Introduction of Rel-16 eMTC enhancements to TS 36.300 | Ericsson |
| R3-201006 | RAN3 TP to R2-1916567 Introduction of Rel-16 NB-IoT enhancements to TS 36.300 | Ericsson |
| R3-201007 | [DRAFT] Reply LS on updates for TS 36.300 and TS 38.300 | Ericsson |
| R3-201065 | Normal inter-RAT HO from SA to EN-DC | Huawei |
| R3-201066 | Inter-RAT HO from SA to EN-DC with shared gNB/sgNB | Huawei |
| R3-201067 | Inter-RAT HO from SA to EN-DC with shared gNB/sgNB | Huawei |
| R3-201068 | Inter-RAT HO from SA to EN-DC with shared gNB/sgNB | Huawei |
| R3-201069 | Inter-RAT HO from SA to EN-DC with shared gNB/sgNB | Huawei |
| R3-201084 | draft Reply LS on inter-RAT HO from SA to EN-DC | China Telecom |
| R3-201088 | Inter-RAT HO from SA to EN-DC with shared gNB/sgNB | Huawei |
| R3-201214 | Summary of offline discussion | Huawei |
| R3-201215 | [DRAFT] Reply LS on handover without SN configuration query | Huawei |
| R3-201216 | draft Reply LS on inter-RAT HO from SA to EN-DC | China Telecom |
| R3-201217 | SA to EN DC handover and direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom |
| R3-201218 | SA to ENDC handover with shared SgNB/gNB | CATT, Nokia, Nokia Shanghai Bell, Samsung, China Telecom,Huawei |
| R3-201219 | SA to EN DC direct forwarding with shared SgNB/gNB | Samsung, Nokia, Nokia Shanghai Bell, CATT, China Telecom |
| R3-201220 | Summary of offline discussion on | Ericsson |
| R3-201221 | Summary of offline discussion on | China Telecom |
| R3-201222 | [DRAFT] Reply LS on Rel-16 NB-IoT enhancements | Huawei |
| R3-201223 | Summary of offline discussion on NB-IoT ench | Huawei |
| R3-201224 | Summary of offline discussion on response LS on Location of UEs and associated key issues | Thales |
| R3-201225 | draft response to SA2 LS on Location of UEs and associated key issues | THALES |
| R3-201271 | RAN3 inputs to RAN2 NB-IoT 36.300 CR | Huawei, Ericsson |
| R3-201272 | RAN3 inputs to RAN2 eMTC 36.300 CR | Huawei, Ericsson |
| R3-201297 | Reply LS on updates for TS 36.300 and TS 38.300 | Ericsson |
| R3-201417 | Reply LS on Rel-16 NB-IoT enhancements | Huawei |
| 8.2 | LSin received during the meeting | |
| R3-201226 | Clarification on encryption requirements for AGF interfaces (N1, N2, N3) [WWC] | Broadband Forum |
| R3-201396 | Reply LS on Sidelink UE Information | RAN2, Ericsson |
| 8.3.1 | RACS | |
| R3-200822 | RACS work in RAN3 | Ericsson |
| 8.3.2 | QoS Monitoring for URLLC | |
| R3-200484 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200485 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200486 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200487 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200488 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200489 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200490 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200491 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200561 | E2E delay measurement for Qos monitoring for URLLC | Huawei |
| R3-200609 | Discussion on F1-U delay measurment for QoS monitoring for URLLC | ZTE |
| R3-200610 | CR for NR-U delay measurement to TS38.425 | ZTE |
| R3-201094 | QoS monitoring support for URLLC | Intel Corporation |
| R3-201095 | (TP for NR_SON_MDT for TS 38.413): QoS monitoring for URLLC | Intel Corporation |
| R3-201096 | (TP for NR_SON_MDT for TS 38.423): QoS monitoring for URLLC | Intel Corporation |
| R3-201097 | (TP for NR_SON_MDT for TS 38.463): QoS monitoring for URLLC | Intel Corporation |
| R3-201098 | (TP for NR_SON_MDT for TS 38.473): QoS monitoring for URLLC | Intel Corporation |
| R3-201099 | (TP for NR_SON_MDT for TS 38.415): QoS monitoring for URLLC | Intel Corporation |
| R3-201100 | (TP for NR_SON_MDT for TS 38.425): QoS monitoring for URLLC | Intel Corporation |
| R3-201101 | [Draft] Reply LS on QoS monitoring for URLLC | Intel Corporation |
| R3-201116 | Summary of offline discussion for CB: # 3_Email003-QoS_monitoring_URLLC | Intel |
| R3-201366 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201367 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201368 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201369 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201370 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201371 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201372 | Reply LS on QoS monitoring for URLLC | Intel Corporation |
| R3-201416 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201431 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201432 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201433 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201434 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201435 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| R3-201436 | E2E delay measurement for Qos monitoring for URLLC | Huawei, Intel Corporation |
| 8.3.3 | Location Information Reporting and DC | |
| R3-200210 | Addition of the PSCell information in the Path Switch procedure | Nokia, Nokia Shanghai Bell |
| R3-200211 | Addition of the PSCell information in the Path Switch procedure | Nokia, Nokia Shanghai Bell |
| R3-200212 | [draft] Response LS on Enhancing Location Information Reporting with Dual Connectivity | Nokia, Nokia Shanghai Bell |
| R3-200334 | PSCell information report for EN-DC for TS36.413 | ZTE Corporation, China Telecom, China Unicom, CMCC |
| R3-200335 | PSCell information report for MR-DC for TS38.413 | ZTE Corporation, China Telecom, China Unicom, CMCC |
| R3-201117 | Summary of offline discussion for CB: # 4_Email004-LocationReportingDC | Nokia |
| R3-201247 | Addition of the PSCell information in the path update procedure | Nokia, Nokia Shanghai Bell, ZTE Corporation, Samsung, China Telecom, China Unicom, CMCC |
| R3-201248 | PSCell information report for EN-DC | ZTE, Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, CMCC, Samsung |
| R3-201249 | Response LS on Enhancing Location Information Reporting with Dual Connectivity | Nokia, Nokia Shanghai Bell |
| 9.2 | LTE | |
| R3-200171 | Correction on Assigned Criticality for Bearer Type | Huawei |
| R3-200174 | WUS impacts on MME paging strategies | Huawei |
| R3-200175 | Support of WUS | Huawei |
| R3-200176 | Support of WUS | Huawei |
| R3-200236 | Correction on Assigned Criticality for Bearer Type | Huawei |
| R3-200826 | Correction of CR1380r2 to explicate procedural interaction | Ericsson |
| R3-200827 | Correction of CR1380r2 to explicate procedural interaction | Ericsson |
| R3-200828 | Correction of tabular representation of the RRC TRANSFER message | Ericsson |
| R3-200829 | Correction of tabular representation of the RRC TRANSFER message | Ericsson |
| R3-200830 | Correction of CR1415r2 – procedure text | Ericsson |
| R3-200831 | Correction of CR1415r2 – procedure text | Ericsson |
| R3-200832 | Remove the “EPC Forbidden” from the Core Network Type Restrictions | Ericsson |
| R3-200836 | Remove the “EPC Forbidden” from the Core Network Type Restrictions | Ericsson |
| R3-201008 | Discussion on capability indication of Rel-15 WUS | Ericsson |
| R3-201235 | Correction of CR1415r2 - procedure text | Ericsson |
| R3-201236 | Correction of CR1415r2 - procedure text | Ericsson |
| R3-201376 | [DRAFT] Reply LS on assistance indication for WUS | Huawei |
| R3-201397 | Reply LS on assistance indication for WUS | Huawei |
| R3-201492 | Correction of tabular representation of the RRC TRANSFER message | Ericsson |
| 9.3 | NR | |
| R3-201232 | Summary of offline discussion on WUS | Huawei |
| R3-201233 | Summary of offline Discussion | Huawei |
| R3-201234 | Summary of offline discussion on … | nn |
| R3-201241 | Summary of offline discussion on … | Ericsson |
| R3-201242 | Summary of offline discussion on … | Nokia |
| R3-201245 | Summary of offline discussion on DC Operation Correction (CB104) | Nokia |
| R3-201413 | Summary of offline discussion on … | Ericsson |
| 9.3.1 | RAN Sharing | |
| R3-200324 | Further discussion on RAN sharing impact over NG interface | ZTE Corporation |
| R3-200325 | Stage3 CR for RAN sharing over NG interface | ZTE Corporation |
| R3-200388 | Further discussion on construction of NCGI when multiple cell IDs are broadcast in SIB1 | Nokia, Nokia Shanghai Bell |
| R3-200639 | Further discussions on NCGI and TAI when multiple cell IDs are broadcast in SIB1 | Huawei, China Telecom, China Unicom |
| R3-200640 | Clarification to 36.300 on constructing NCGI and TAI when multiple cell IDs are broadcast in SIB1 | Huawei, China Telecom, China Unicom |
| R3-200641 | Clarification to 36.300 on constructing NCGI and TAI when multiple cell IDs are broadcast in SIB1 | Huawei, China Telecom, China Unicom |
| R3-200642 | Clarification to 38.300 on constructing NCGI and TAI when multiple cell IDs are broadcast in SIB1 | Huawei, China Telecom, China Unicom |
| R3-200643 | Clarification to 38.300 on constructing NCGI and TAI when multiple cell IDs are broadcast in SIB1 | Huawei, China Telecom, China Unicom |
| R3-200775 | Construction of NCGI when multiple cell IDs are broadcast in SIB1 | Nokia, Nokia Shanghai Bell |
| R3-200833 | RAN Sharing and Global RAN node Identifiers | Ericsson |
| R3-200834 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200835 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200837 | RAN Sharing and Global RAN node Identifiers | Ericsson |
| R3-200838 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200839 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200840 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200841 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200842 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200843 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200844 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200845 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200848 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200849 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200852 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200853 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200856 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-200857 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-201118 | Summary of offline discussion for CB: # 5_Email005-RAN_sharing | Ericsson |
| R3-201315 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-201316 | eNB node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-201317 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| R3-201318 | NG-RAN node identification in case it is associated with more than one PLMN ID | Ericsson |
| 9.3.2 | NR Restriction | |
| R3-200286 | Handover and Mobility Restriction List over multiple releases | Qualcomm Incorporated |
| R3-200846 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | Ericsson |
| R3-200847 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | Ericsson |
| R3-200850 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | Ericsson |
| R3-200851 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | Ericsson |
| R3-200854 | Propagation of Roaming and Access Restriction information in RAN in non-homogenous RAN node deployments | Ericsson |
| R3-200859 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | Ericsson |
| R3-200860 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | Ericsson |
| R3-200862 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | Ericsson |
| R3-200863 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | Ericsson |
| R3-200864 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | Ericsson |
| R3-200865 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | Ericsson |
| R3-200866 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | Ericsson |
| R3-200867 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | Ericsson |
| R3-200868 | Propagation of Roaming and Access Restriction information in RAN in non-homogenous RAN node deployments | Ericsson |
| R3-201119 | Summary of offline discussion for CB: # 6_Email006-Roaming_and_access_restrictions | Ericsson |
| R3-201258 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | Ericsson |
| R3-201259 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | Ericsson |
| R3-201260 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | Ericsson |
| R3-201261 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | Ericsson |
| 9.3.3 | NAS Non Delivery | |
| R3-200138 | Correction of NAS Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-200139 | Correction of NAS Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-200140 | Correction of NAS Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-200141 | Correction of NAS Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-200142 | Correction of NAS Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-200855 | Discussions on NAS Non Delivery issues | Ericsson |
| R3-200858 | [DRAFT] LS on NAS non Delivery Indication | Ericsson |
| R3-200869 | Discussions on NAS Non Delivery issues | Ericsson |
| R3-200870 | Clarification of the two levels NAS PDU | Ericsson |
| R3-200871 | Clarification of the two levels NAS PDU | Ericsson |
| R3-200922 | [DRAFT] LS on NAS non Delivery Indication | Ericsson |
| R3-201120 | Summary of offline discussion for CB: # 7_Email007-NAS_non-delivery | Nokia |
| R3-201362 | LS on NAS Non delivery for RRC Inactive state | Nokia |
| 9.3.4 | SgNB Initiated SgNB Modification | |
| R3-200449 | Discussion on open issue for nested SN modification procedure | CATT |
| R3-200450 | Correction on nested SN modification procedure | CATT |
| R3-200451 | Correction on nested SN modification procedure | CATT |
| R3-201121 | Summary of offline discussion for CB: # 8_Email008-SgNBinit_SgNBmod | CATT |
| R3-201325 | Correction on nested SN modification procedure | CATT |
| R3-201326 | Correction on nested SN modification procedure | CATT |
| R3-201327 | Correction on nested SN modification procedure | CATT |
| R3-201328 | Correction on nested SN modification procedure | CATT |
| 9.3.5 | E-RAB ID in Modification Procedure | |
| R3-200143 | Correction of E-RAB ID revoke | Nokia, Nokia Shanghai Bell |
| R3-200144 | Correction of E-RAB ID revoke | Nokia, Nokia Shanghai Bell |
| R3-200145 | Correction of E-RAB ID revoke | Nokia, Nokia Shanghai Bell |
| R3-200654 | E-RAB ID revocation in modification procedure | Huawei |
| R3-200655 | E-RAB ID revocation in modification procedure | Huawei |
| R3-200656 | E-RAB ID revocation in modification procedure | Huawei |
| R3-200925 | Handling the IE in the modification messages | Ericsson |
| R3-200926 | Handling the IE in the modification messages | Ericsson |
| R3-201122 | Summary of offline discussion for CB: # 9_Email009-E-RAB_ID_in_revoke | Ericsson |
| 9.3.6 | Intra-DU Handover | |
| R3-200555 | Discussion on RRC Message Transfer for Intra-DU Handover | ZTE Corporation |
| R3-200649 | Further discussions on intra-DU HO | Huawei |
| R3-200796 | Considerations regarding intra-DU HO | Ericsson |
| R3-200861 | Considerations regarding intra-DU HO | Ericsson |
| R3-200930 | Considerations regarding intra-DU HO | Ericsson |
| R3-201123 | Summary of offline discussion for CB: # 10_Email010-Intra-DU_HO | ZTE |
| 9.3.8.1 | Other Corrections | |
| R3-200146 | Correction of removal of last pdu session | Nokia, Nokia Shanghai Bell, Orange |
| R3-200147 | Correction of removal of last pdu session | Nokia, Nokia Shanghai Bell, Orange |
| R3-200148 | Correction of removal of last pdu session | Nokia, Nokia Shanghai Bell, Orange |
| R3-200149 | Correction of DC Operation Mode | Nokia, Nokia Shanghai Bell, Orange |
| R3-200150 | Correction of DC Operation Mode | Nokia, Nokia Shanghai Bell, Orange |
| R3-200151 | Correction of DC Operation Mode | Nokia, Nokia Shanghai Bell, Orange |
| R3-200274 | Discussion on DRB ID transfer during handover without SCG configuration query | ZTE |
| R3-200275 | CR36.423 for DRB exchange on inter MN handover without SN configuration query | ZTE |
| R3-200276 | CR38.423 for DRB exchange on inter MN handover without SN configuration query | ZTE |
| R3-200277 | CR37.340 for DRB exchange on inter MN handover without SN configuration query | ZTE |
| R3-200293 | Correction of Warning Security Information in ETWS primary notification | Nokia, Nokia Shanghai Bell |
| R3-200294 | Correction of Warning Security Information in ETWS primary notification | Nokia, Nokia Shanghai Bell |
| R3-200295 | Correction of PWS Failure Indication | Nokia, Nokia Shanghai Bell |
| R3-200296 | Correction of PWS Failure Indication | Nokia, Nokia Shanghai Bell |
| R3-200297 | Correction of tabular for Xn TNL Configuration Info | Nokia, Nokia Shanghai Bell |
| R3-200298 | Correction of tabular for Xn TNL Configuration Info | Nokia, Nokia Shanghai Bell |
| R3-200317 | TS36.423 Reformulation of X2AP Procedure Text as Receiving Node | ZTE |
| R3-200318 | TS38.423 Reformulation of XnAP Procedure Text as Receiving Node | ZTE |
| R3-200344 | Correction of the presence of UL UP TNL Information to be setup List IE in tabular | NEC, Samsung |
| R3-200345 | Correction of the presence of UL UP TNL Information to be setup List IE in tabular | NEC, Samsung |
| R3-200346 | Correction of the referred RRCResumeRequest1 | NEC |
| R3-200347 | Correction of the referred RRCResumeRequest1 name | NEC |
| R3-200448 | Correction on AS rekeying handling | CATT |
| R3-200452 | Discussion on the open issue for location report | CATT |
| R3-200453 | Correction on location report-Optiion 1 | CATT |
| R3-200454 | Correction on location report-Optiion 2 | CATT |
| R3-200455 | Correction on handover related timer | CATT |
| R3-200644 | Clarification to broadcast PLMN list under RAN sharing case | Huawei, China Telecom, China Unicom |
| R3-200645 | Clarification to broadcast PLMN list under RAN sharing case | Huawei, China Telecom, China Unicom |
| R3-200646 | Clarification to broadcast PLMN list under RAN sharing case | Huawei, China Telecom, China Unicom |
| R3-200647 | Clarification to broadcast PLMN list under RAN sharing case | Huawei, China Telecom, China Unicom |
| R3-200657 | Correction of RAN paging priority | Huawei |
| R3-200658 | Correction of RAN paging priority | Huawei |
| R3-200659 | PDU session resource in UE context release | Huawei |
| R3-200660 | PDU session resource in UE context release | Huawei |
| R3-200661 | Clarification of RAT restriction in mobility restriction list | Huawei |
| R3-200662 | Clarification of RAT restriction in mobility restriction list | Huawei |
| R3-200663 | Clarification of RAT restriction in mobility restriction list | Huawei |
| R3-200664 | Clarification of RAT restriction in mobility restriction list | Huawei |
| R3-200744 | Misalignment between the tabular and ASN.1 within the SN modification procedure | Samsung |
| R3-200745 | Misalignment between the tabular and ASN.1 within the SN modification procedure | Samsung |
| R3-200768 | Clarification to Semantics description of 5GS TAC and Served PLMN | China Telecom Corporation Ltd. |
| R3-200769 | CR to TS 36.423 on semantics description of 5GS TAC and Served PLMN | China Telecom Corporation Ltd. |
| R3-200931 | Correction of CR0236r2 to explicate procedural interaction | Ericsson |
| R3-200932 | Correction of CR0236r2 to explicate procedural interaction | Ericsson |
| R3-200933 | Correction of CR0282r1 – procedure text | Ericsson |
| R3-200934 | Correction of CR0282r1 – procedure text | Ericsson |
| R3-200935 | Correction relating to Initial UL RRC Message Transfer procedure CR 38.473 | Ericsson |
| R3-200936 | RRC Reconfiguration in DU initiated UE Context Modification Required CR 38.473 | Ericsson |
| R3-200937 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson |
| R3-200938 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson |
| R3-200939 | Clarification the usage of the New AMF UE NGAP ID included in the UE CONTEXT MODIFICATION REQUEST message | Ericsson |
| R3-200940 | Clarification the usage of the New AMF UE NGAP ID included in the UE CONTEXT MODIFICATION REQUEST message | Ericsson |
| R3-201237 | Correction of PWS Failure Indication | Nokia, Nokia Shanghai Bell |
| R3-201238 | Correction of PWS Failure Indication | Nokia, Nokia Shanghai Bell |
| R3-201239 | Correction relating to Initial UL RRC Message Transfer procedure CR 38.473 | Ericsson |
| R3-201240 | Correction relating to Initial UL RRC Message Transfer procedure CR 38.473 | Ericsson |
| R3-201243 | Correction of removal of last pdu session | Nokia, Nokia Shanghai Bell, Orange |
| R3-201244 | Correction of removal of last pdu session | Nokia, Nokia Shanghai Bell, Orange |
| R3-201252 | Misalignment between the tabular and ASN.1 within the SN modification procedure | Samsung |
| R3-201262 | Correction of CR0282r1 - procedure text | Ericsson |
| R3-201263 | Correction of CR0282r1 - procedure text | Ericsson |
| R3-201273 | Correction on AS rekeying handling | CATT |
| R3-201274 | Correction on AS rekeying handling | CATT |
| R3-201275 | Correction on handover related timer | CATT |
| R3-201276 | Summary on CB: # 106_HO_Timer_handling | CATT |
| R3-201277 | Summary on CB: # 105_OptionalIEs_incl_security_key | CATT |
| R3-201278 | PDU session resource in UE context release | Huawei |
| R3-201279 | PDU session resource in UE context release | Huawei |
| R3-201280 | Summary of offline discussion on PDU session resource in UE context release | Huawei |
| R3-201493 | Correction relating to Initial UL RRC Message Transfer procedure CR 38.473 | Ericsson |
| 9.3.8.2 | Pure Stage-2 Corrections | |
| R3-200872 | Corrections to Stage 2 ANR description | Ericsson |
| R3-200873 | Corrections to Stage 2 ANR description | Ericsson |
| R3-200941 | Corrections to Stage 2 ANR description | Ericsson |
| R3-200942 | Corrections to Stage 2 ANR description | Ericsson |
| 10.1 | General | |
| R3-200003 | Addition of SON feature | Huawei |
| R3-200004 | Addition of SON feature | Huawei |
| R3-200005 | Addition of MDT features | ZTE |
| R3-200006 | Addition of MDT features | Samsung Electronics Co., Ltd |
| R3-200007 | Addition of MDT features | Samsung Electronics Co., Ltd |
| R3-200008 | MDT configuration support for XnAP | Ericsson |
| R3-200009 | Addition of SON features | Huawei |
| R3-200010 | Addition of SON feature | CATT |
| R3-200011 | Addition of MDT feature | Huawei |
| R3-200012 | Addition of SON feature | Samsung |
| R3-200013 | Addition of SON features | Ericsson |
| R3-200014 | Addition of SON feature | Huawei |
| R3-200015 | Addition of SON feature | CMCC,Huawei |
| R3-200585 | Updated work plan for SON and MDT WI | CMCC |
| R3-200586 | BLCR to 38.420: Addition of MDT feature | CMCC |
| R3-200587 | BLCR to 38.420: Addition of SON feature | CMCC |
| R3-200588 | BLCR to 38.470: Addition of SON feature | CMCC |
| R3-200589 | BLCR to 38.460: Addition of SON feature | CMCC |
| R3-200767 | MDT Configuration support for XnAP | Ericsson |
| R3-200874 | MRO OAM requirement description TP 38.300 | Ericsson |
| R3-200943 | MRO OAM requirement description TP 38.300 | Ericsson |
| R3-201124 | Summary of offline discussion for CB: # 20_Email020-SONMDT_BL_CRs | CMCC |
| R3-201473 | Addition of SON features | Huawei |
| R3-201474 | Addition of SON feature | CATT |
| R3-201475 | Addition of SON features | CMCC, Huawei |
| R3-201476 | Addition of MDT features | Samsung |
| R3-201477 | Addition of SON features | Huawei |
| R3-201478 | Addition of MDT feature | Huawei |
| R3-201479 | Addition of SON features | Samsung |
| R3-201480 | MDT Configuration support for XnAP | Ericsson |
| R3-201481 | Addition of SON features | Ericsson |
| R3-201482 | Addition of MDT features | ZTE |
| R3-201483 | Addition of SON features | Huawei |
| R3-201484 | Addition of MDT features | Samsung |
| 10.2.1.1 | Intra-System and Inter-System Connection Failure | |
| R3-200364 | (TP for SON BL CR for TS 38.413): Intra-System and Inter-System Connection Failure | Huawei |
| R3-200365 | (TP for SON BL CR for TS 38.423): Intra-System and Inter-System Connection Failure | Huawei |
| R3-200432 | (TP on SON BLCR for 38.423) Finalization of intra-system connection failure | CATT |
| R3-200574 | (TP for SON BL CR for TS 38.300): MRO | Samsung |
| R3-200575 | (TP for SON BL CR for TS 38.413): Connection Failure | Samsung |
| R3-200576 | (TP for SON BL CR for TS 38.423): Connection Failure | Samsung |
| R3-200611 | (TP for [NR_SON_MDT] BL CR for TS 38.300) Addition of SON features | ZTE |
| R3-200875 | Signalling of RLF Report to gNB-DU TP 38.473 | Ericsson |
| R3-200876 | Signalling of Connection Establishment Failure from gNB-CU to gNB-DU TP 38.473 | Ericsson |
| R3-200877 | Handling of RLF in the gNB-DU TP 38.473 | Ericsson |
| R3-200878 | Xn Signalling for Accessibility Measurement | Ericsson |
| R3-200879 | Addition of SON features TP 38.300 | Ericsson |
| R3-200944 | Signalling of RLF Report to gNB-DU TP 38.473 | Ericsson |
| R3-200945 | Signalling of Connection Establishment Failure from gNB-CU to gNB-DU TP 38.473 | Ericsson |
| R3-200946 | Handling of RLF in the gNB-DU TP 38.473 | Ericsson |
| R3-200947 | Xn Signalling for Accessibility Measurement | Ericsson |
| R3-200948 | Addition of SON features TP 38.300 | Ericsson |
| R3-201125 | Summary of offline discussion for CB: # 21_Email021-Conn_Fail | Huawei |
| R3-201323 | (TP for SON BL CR for TS 38.413): Intra-System and Inter-System Connection Failure | Huawei |
| R3-201324 | TP to SON BLCR 38.300 on MRO OAM requirement corrections | CMCC |
| R3-201338 | (TP for SON BL CR for TS 38.423): Intra-System and Inter-System Connection Failure | Samsung |
| 10.2.1.2 | Inter-System Ping-Pong and Unnecessary Handover | |
| R3-200366 | (TP for SON BL CR for TS 36.413): Clarification to unnecessary HO | Huawei |
| R3-200367 | (TP for SON BL CR for TS 38.413): Clarification to unnecessary HO | Huawei |
| R3-200431 | (TP on SON BLCR for 36.413) Finalization of inter-system unnecessary HO | CATT |
| R3-200577 | (TP for SON BL CR for TS 36.413): Inter-system unnecessary handover | Samsung |
| R3-200673 | (TP for SON BL CR for TS 38.423): Clarification to inter-system ping-pong | Huawei |
| R3-200674 | (TP for SON BL CR for TS 38.300): Clarification to inter-system ping-pong and unnecessary HO | Huawei |
| R3-200880 | Examination of FFSs in SON BL CR for TS 36.413 | Ericsson |
| R3-200949 | Examination of FFSs in SON BL CR for TS 36.413 | Ericsson |
| R3-201126 | Summary of offline discussion for CB: # 22_Email022-InterSysPingPong | Ericsson |
| R3-201331 | (TP on SON BL CR for TS 38.413) Correction on intersystem unnecessary HO (CATT) | CATT |
| R3-201386 | Examination of FFSs in SON BL CR for TS 36.413 | Ericsson |
| R3-201414 | Examination of FFSs in SON BL CR for TS 36.413 | Ericsson |
| 10.2.1.3 | SN Change Failure | |
| R3-200074 | Further discussion on MRO for SN change failure | Nokia, Nokia Shanghai Bell |
| R3-200441 | Consideration on support of MRO for SN change in case of MR-DC | CATT |
| R3-200442 | [draft]LS to RAN2 on MRO for SN change | CATT |
| R3-200572 | (TP for SON BL CR for TS 38.423) Solution for SN change failure | Samsung |
| R3-200573 | (TP for SON BL CR for TS 38.423) Newprocedure for SN change failure report | Samsung |
| R3-200612 | Detection solution for SN change failure | ZTE |
| R3-200613 | (TP for [NR_SON_MDT] BL CR for TS 38.300) Detection solution for SN change failure | ZTE |
| R3-200614 | (TP for [NR_SON_MDT] BL CR for TS 38.423) Detection solution for SN change failure | ZTE |
| R3-201127 | Summary of offline discussion for CB: # 23_Email023-SN_change_failure | ZTE |
| 10.2.1.4 | CU-DU Aspects for MRO | |
| R3-200313 | RLF information signaling between gNB-CU and gNB-DU | LG Electronics |
| R3-200314 | (TP for NR_SON_MDT BL CR for TS 38.473): RLF information signaling between gNB-CU and gNB-DU | LG Electronics |
| R3-200881 | Signalling of RLF information between gNB-CU and gNB-DU | Ericsson |
| R3-200950 | Signalling of RLF information between gNB-CU and gNB-DU | Ericsson |
| R3-201128 | Summary of offline discussion for CB: # 24_Email024-CU-DU_MRO | LG |
| 10.2.1.5 | Successful Handover Report | |
| R3-200636 | (TP for SON BL CR for TS 38.413) Successful HO report for MRO | BEIJING SAMSUNG TELECOM R&D |
| 10.2.1.6 | UE Reported Mobility History | |
| R3-200368 | (TP for SON BL CR for TS 38.300) UE reported history information | Huawei, BT, CUC |
| R3-200369 | (TP for SON BL CR for TS 38.423) UE reported history information | Huawei, BT, CUC |
| R3-200370 | (TP for SON BL CR for TS 38.413) UE reported history information | Huawei, BT, CUC |
| R3-200404 | Mobility history from UE | Qualcomm Incorporated |
| R3-200405 | (TP for SON BL CR for 38.413) Mobility history from UE | Qualcomm Incorporated |
| R3-200406 | (TP for SON BL CR for 38.423) Mobility history from UE | Qualcomm Incorporated |
| R3-200428 | Discussion on UE history information in handover preparation procedures | CATT |
| R3-200429 | (TP on SON BLCR for 38.413)Addition of UE history information in handover preparation procedures | CATT |
| R3-200430 | (TP on SON BL CR for 38.423)Addition of UE history information in handover preparation procedures | CATT |
| R3-200592 | UE reported mobility history information for NR | CMCC |
| R3-200593 | TP to SON BLCR 38.413 on UE reported mobility history infomation | CMCC |
| R3-200594 | TP to SON BLCR 38.423 on UE reported mobility history infomation | CMCC |
| R3-200615 | (TP for [NR_SON_MDT] BL CR for TS 38.300)Introduce UE history information from the UE | ZTE |
| R3-200616 | (TP for [NR_SON_MDT] BL CR for TS 38.413)Introduce UE history information from the UE | ZTE |
| R3-200617 | (TP for [NR_SON_MDT] BL CR for TS 38.423)Introduce UE history information from the UE | ZTE |
| R3-200746 | NR mobility history information stored by UE | LG Electronics |
| R3-200747 | (TP for NR_SON_MDT BL CR for TS 38.413) NR mobility history information stored by UE | LG Electronics |
| R3-200748 | (TP for NR_SON_MDT BL CR for TS 38.423) NR mobility history information stored by UE | LG Electronics |
| R3-201129 | Summary of offline discussion for CB: # 26_Email026-UErepMobHistory | Huawei |
| R3-201378 | (TP for [NR_SON_MDT] BL CR for TS 38.300)Introduce UE history information from the UE | ZTE |
| R3-201410 | (TP for MDT BL CR for TS 38.463): )Addition of MDT | ZTE |
| 10.2.2.1 | MLB for Xn/X2/F1/E1 | |
| R3-200075 | Metric for radio load | Nokia, Nokia Shanghai Bell |
| R3-200076 | [DRAFT] LS on metric for radio load | Nokia, Nokia Shanghai Bell |
| R3-200371 | (TP for SON BL CR for TS 38.423): MLB | Huawei |
| R3-200372 | (TP for SON BL CR for TS 38.473): MLB | Huawei |
| R3-200373 | (TP for SON BL CR for TS 36.423): MLB | Huawei |
| R3-200374 | (TP for SON BL CR for TS 38.463): MLB | Huawei |
| R3-200375 | (TP for SON BL CR for TS 38.300): Mobility settings change | Huawei |
| R3-200376 | (TP for SON BL CR for TS 38.423): Mobility settings change | Huawei |
| R3-200382 | Discussion on TNL load reports | Nokia, Nokia Shanghai Bell |
| R3-200383 | Averaging window for periodic and not periodic load measurement | Nokia, Nokia Shanghai Bell |
| R3-200433 | Correction on MLB | CATT |
| R3-200434 | (TP on SON BL CR for TS 38.423) Correction on MLB | CATT |
| R3-200435 | (TP on SON BL CR for TS 38.473) Correction on MLB | CATT |
| R3-200436 | (TP on SON BL CR for TS 36.423) Correction on MLB | CATT |
| R3-200595 | Remaining issues of MLB | CMCC |
| R3-200596 | TP to SON BLCR 38.300 on support of MLB | CMCC |
| R3-200618 | Mobility Settings Change procedure for MRO/MLB | ZTE |
| R3-200619 | (TP for [NR_SON_MDT] BL CR for TS 38.300)Mobility Settings Change procedure for MROMLB | ZTE |
| R3-200620 | Further Discussion on Metrics for MLB | ZTE |
| R3-200621 | TP for [NR_SON_MDT] BL CR for TS 36.423) Addition of MLB Features | ZTE |
| R3-200622 | TP for [NR_SON_MDT] BL CR for TS 38.423) Addition of MLB Features | ZTE |
| R3-200623 | TP for [NR_SON_MDT] BL CR for TS 38.473) Addition of MLB Features | ZTE |
| R3-200672 | Further consideration on active UEs | NTT DOCOMO INC. |
| R3-200736 | (TP for SON BL CR on 36.423) Addition of active UEs in load reporting | NTT DOCOMO INC. |
| R3-200737 | (TP for SON BL CR on 38.423) Addition of active UEs in load reporting | NTT DOCOMO INC. |
| R3-200738 | (TP for SON BL CR on 38.473) Addition of active UEs in load reporting | NTT DOCOMO INC. |
| R3-200772 | (TP for SON BL CR for TS 38.423) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-200773 | (TP for SON BL CR for TS 38.463) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-200774 | (TP for SON BL CR for TS 38.473) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-200882 | Addition of SON features - CR to BL TP for 38.423 for MLB | Ericsson |
| R3-200883 | Addition of SON features – CR to BL TP to 38.473 for MLB | Ericsson |
| R3-200884 | Addition of SON features - CR to BL TP for 38.463 for MLB | Ericsson |
| R3-200885 | Addition of SON feature - - CR to BL TP for 36.423 for MLB | Ericsson |
| R3-200886 | Mobility Settings Change procedure for NG RAN | Ericsson |
| R3-200887 | Addition of SON features – CR to BL TP for 38.423 for Mobility settings change | Ericsson |
| R3-200888 | Discussion on remaining FFS for MLB in Rel-16 | Ericsson |
| R3-200951 | Addition of SON features - CR to BL TP for 38.423 for MLB | Ericsson |
| R3-200952 | Addition of SON features – CR to BL TP to 38.473 for MLB | Ericsson |
| R3-200953 | Addition of SON features - CR to BL TP for 38.463 for MLB | Ericsson |
| R3-200954 | Addition of SON feature - - CR to BL TP for 36.423 for MLB | Ericsson |
| R3-200955 | Mobility Settings Change procedure for NG RAN | Ericsson |
| R3-200956 | Addition of SON features – CR to BL TP for 38.423 for Mobility settings change | Ericsson |
| R3-200957 | Discussion on remaining FFS for MLB in Rel-16 | Ericsson |
| R3-201130 | Summary of offline discussion for CB: # 27_Email027-MLB_Xn_X2_F1_E1 | Nokia |
| R3-201330 | (TP on SON BL CR for TS 36.423) Correction on MLB | CATT |
| R3-201346 | (TP for SON BL CR for TS 38.473): MLB | Huawei |
| R3-201374 | TP to SON BLCR 38.300 on support of MLB | CMCC |
| R3-201380 | (TP for SON BL CR for TS 38.463) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-201400 | Addition of SON features - CR to BL TP for 38.423 for MLB | Ericsson |
| R3-201404 | (TP on SON BL CR for TS 36.423) Correction on MLB | CATT |
| R3-201405 | (TP for SON BL CR for TS 38.473): MLB | Huawei |
| R3-201406 | (TP for SON BL CR for TS 38.463) Load reporting updates | Nokia, Nokia Shanghai Bell |
| 10.2.2.3 | MLB for MR-DC | |
| R3-200624 | TP for [NR_SON_MDT] BL CR for TS 36.423) Addition of MLB for EN-DC | ZTE |
| R3-201131 | Summary of offline discussion for CB: # 28_Email028-MLB_for_MR-DC | ZTE |
| 10.2.3 | RACH Optimization | |
| R3-200163 | RACH Optimization Enhancement for NR | China Telecom Corporation Ltd. |
| R3-200164 | RACH Optimization Enhancement for NR | China Telecom Corporation Ltd. |
| R3-200165 | CR to 36.423 for supporting PRACH Configuration exchange in EN-DC | China Telecom Corporation Ltd. |
| R3-200166 | CR to 38.423 for supporting PRACH Configuration exchange | China Telecom Corporation Ltd. |
| 10.2.3.1 | RACH Optimization Enhancements | |
| R3-200437 | Discussion on PRACH coordination | CATT |
| R3-200438 | (TP on SON BL CR for TS 38.300) Addition of PRACH Coordination | CATT |
| R3-200439 | (TP on SON BL CR for TS 38.423) Addition of PRACH Coordination | CATT |
| R3-200440 | (TP on SON BL CR for TS 38.473) Addition of PRACH Coordination | CATT |
| R3-200492 | (TP for SON BL CR for TS 38.473): UE RACH Report for RACH Optimization | Huawei |
| R3-200493 | (TP for SON BL CR for TS 38.423): UE RACH Report for RACH Optimization | Huawei |
| R3-200590 | Addition of RACH Optimization Feature | CMCC, Huawei |
| R3-200591 | TP to SON BLCR 38.300 on support of RACH optimization | CMCC, Huawei |
| R3-200625 | Left issue for NR RACH Optimization | ZTE |
| R3-200626 | (TP for [NR_SON_MDT] BL CR for TS 38.300)Addition of RACH OPTIMIZATION | ZTE |
| R3-200627 | (TP for [NR_SON_MDT] BL CR for TS 38.423)Addition of RACH OPTIMIZATION | ZTE |
| R3-200628 | (TP for [NR_SON_MDT] BL CR for TS 38.473)Addition of RACH OPTIMIZATION | ZTE |
| R3-200889 | Signalling of RACH Report from gNB-CU to gNB-DU | Ericsson |
| R3-200890 | Solution for RACH Optimisation over the Xn | Ericsson |
| R3-200958 | Signalling of RACH Report from gNB-CU to gNB-DU | Ericsson |
| R3-200959 | Solution for RACH Optimisation over the Xn | Ericsson |
| R3-201132 | Summary of offline discussion for CB: # 29_Email029-RACHopt_enhs | CATT |
| R3-201329 | (TP on SON BL CR for TS 38.423) Addition of PRACH Coordination | CATT |
| R3-201389 | Addition of RACH Optimization Feature | CMCC, Huawei |
| R3-201390 | TP to SON BLCR 38.300 on support of RACH optimization | CMCC, Huawei |
| 10.2.3.2 | Configuration Conflicts for RACH Optimization | |
| R3-200385 | RACH Assistance Information Exchange | Nokia, Nokia Shanghai Bell |
| R3-200386 | (TP for SON BL CR for TS 38.473) Introduction of RACH Assistance Information | Nokia, Nokia Shanghai Bell |
| R3-200387 | (TP for SON BL CR for TS 38.423) Introduction of RACH Assistance Information | Nokia, Nokia Shanghai Bell |
| R3-200494 | (TP for SON BL CR for TS 38.423): PRACH configuration exchange | Huawei, CMCC |
| R3-200495 | (TP for SON BL CR for TS 38.473): PRACH configuration exchange | Huawei, CMCC |
| R3-200891 | Solution for RACH Conflict Detection and Resolution at gNB-DU | Ericsson |
| R3-200892 | Addition of RACH Optimization Feature on F1 interface | Ericsson |
| R3-200960 | Solution for RACH Conflict Detection and Resolution at gNB-DU | Ericsson |
| R3-200961 | Addition of RACH Optimization Feature on F1 interface | Ericsson |
| R3-201133 | Summary of offline discussion for CB: # 30_Email030-Config_conflicts_RACHopt | Nokia |
| R3-201347 | (TP for SON BL CR for TS 38.473): PRACH configuration exchange | Huawei, CMCC |
| 10.3.1 | MDT Activation and Reporting | |
| R3-200384 | (TP for MDT BL CR for TS 38.473) Addition of MDT for intra-DU inter-cell mobility scenarios | Nokia, Nokia Shanghai Bell |
| R3-200401 | User consent support for MDT | Qualcomm Incorporated |
| R3-200402 | (TP for MDT BL CR for 38.413) User consent support for MDT | Qualcomm Incorporated |
| R3-200403 | (TP for MDT BL CR for 38.423) User consent support for MDT | Qualcomm Incorporated |
| R3-200496 | (TP for MDT BL CR for TS 38.413): MDT measurement IEs design | Huawei |
| R3-200497 | (TP for MDT BL CR for TS 38.423): MDT measurement IEs design | Huawei |
| R3-200498 | (TP for MDT BL CR for TS 38.473): MDT measurement IEs design | Huawei |
| R3-200499 | (TP for MDT BL CR for TS 38.463): MDT measurement IEs design | Huawei |
| R3-200515 | Discussion the open issues for MDT | BEIJING SAMSUNG TELECOM R&D |
| R3-200516 | (TP for MDT BL for 38.463) Text Proposal for Cell Traffic Trace | BEIJING SAMSUNG TELECOM R&D |
| R3-200517 | (TP for MDT BL for 38.473) Text Proposal for Cell Traffic Trace | BEIJING SAMSUNG TELECOM R&D |
| R3-200518 | (TP for MDT BL CR for 38.401) Addition of management based MDT activation | BEIJING SAMSUNG TELECOM R&D |
| R3-200519 | (TP for MDT BL for 38.423) Propagation for Management Based MDT PLMN List | BEIJING SAMSUNG TELECOM R&D |
| R3-200548 | Addition of MDT feature | BEIJING SAMSUNG TELECOM R&D |
| R3-200629 | Left issue for MDT | ZTE |
| R3-200630 | (TP for [NR_SON_MDT] BL CR for TS 38.463)Addition of MDT | ZTE |
| R3-200631 | (TP for [NR_SON_MDT] BL CR for TS 38.473)Addition of MDT | ZTE |
| R3-200632 | (TP for [NR_SON_MDT] BL CR for TS 38.413)Signalling based immediate MDT continuity upon handover | ZTE |
| R3-200893 | Addition of DC related MDT features in 38.401 TP | Ericsson |
| R3-200894 | Cell Traffic Trace over F1 TP | Ericsson |
| R3-200895 | Cell Traffic Trace over E1 TP | Ericsson |
| R3-200896 | Event Triggered Logged MDT on NGAP TP | Ericsson |
| R3-200897 | Event Triggered Logged MDT on XnAP TP | Ericsson |
| R3-200963 | Cell Traffic Trace over F1 TP | Ericsson |
| R3-200964 | Cell Traffic Trace over E1 TP | Ericsson |
| R3-200965 | Event Triggered Logged MDT on NGAP TP | Ericsson |
| R3-200966 | Event Triggered Logged MDT on XnAP TP | Ericsson |
| R3-200968 | Addition of management based MDT in 38.401 TP | Ericsson |
| R3-201134 | Summary of offline discussion for CB: # 31_Email031-MDTactivation_reporting | Samsung |
| R3-201320 | (TP for MDT BL CR for TS 38.413): MDT measurement IEs design | Huawei |
| R3-201333 | (TP for MDT BL for 38.473) Text Proposal for Cell Traffic Trace | BEIJING SAMSUNG TELECOM R&D |
| R3-201334 | (TP for MDT BL CR for 38.401) Addition of management based MDT activation | BEIJING SAMSUNG TELECOM R&D |
| R3-201360 | (TP for [NR_SON_MDT] BL CR for TS 38.463)Addition of MDT | ZTE |
| R3-201391 | LS on removal of Management Based MDT Allowed IE for NR | Qualcomm |
| R3-201399 | Event Triggered Logged MDT on XnAP TP | Ericsson |
| R3-201401 | Summary of offline discussion for CB: # 31_Email031-MDTactivation_reporting | Samsung |
| R3-201407 | (TP for MDT BL CR for TS 38.413): MDT measurement IEs design | Huawei |
| R3-201408 | (TP for MDT BL for 38.473) Text Proposal for Cell Traffic Trace | BEIJING SAMSUNG TELECOM R&D |
| R3-201409 | (TP for MDT BL CR for 38.401) Addition of management based MDT activation | BEIJING SAMSUNG TELECOM R&D |
| R3-201411 | LS on removal of Management Based MDT Allowed IE for NR | Qualcomm |
| R3-201437 | LS on removal of Management Based MDT Allowed IE for NR | Qualcomm |
| 10.3.2 | MDT for Inactive UEs | |
| R3-200898 | Logged MDT availability indicator signal over Xn | Ericsson |
| R3-200967 | Logged MDT availability indicator signal over Xn | Ericsson |
| R3-201135 | Summary of offline discussion for CB: # 32_Email032-MDT_inactiveUEs | Ericsson |
| 10.3.3 | MDT for MR-DC | |
| R3-200407 | MDT for EN-DC | Qualcomm Incorporated |
| R3-200408 | (BL CR for 36.423) MDT for EN-DC | Qualcomm Incorporated |
| R3-200409 | (BL CR for 36.413) MDT for EN-DC | Qualcomm Incorporated |
| R3-200443 | Support of MDT configuration for EN-DC scenario | CATT |
| R3-200444 | (TP on MDT BL CR for 36.413)Support of MDT configuration for EN-DC scenario | CATT |
| R3-200445 | (TP on MDT BL CR for 36.423)Support of MDT configuration for EN-DC scenario | CATT |
| R3-200500 | MDT support for EN-DC | Huawei |
| R3-200501 | MDT support for EN-DC | Huawei |
| R3-200502 | MDT support for EN-DC | Huawei |
| R3-200633 | Addition of EN-DC MDT feature | ZTE |
| R3-200634 | CR for EN-DC MDT Configuration support for S1AP | ZTE |
| R3-200635 | CR for EN-DC MDT Configuration support for X2AP | ZTE |
| R3-200899 | Addition of management based MDT in 38.401 TP | Ericsson |
| R3-200962 | Addition of DC related MDT features in 38.401 TP | Ericsson |
| R3-201136 | Summary of offline discussion for CB: # 33_Email033-MDT_EN-DC | Huawei |
| R3-201321 | MDT support for EN-DC | Huawei |
| R3-201322 | MDT support for EN-DC | Huawei |
| R3-201430 | MDT support for EN-DC | Huawei, SAMSUNG |
| 12.1 | General | |
| R3-200290 | Work plan for LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| 12.2 | Network Signaling for MBMS Dedicated Networks | |
| R3-200291 | Impacts of LTE-based 5G terrestrial broadcast on RAN3 specifications | Qualcomm Incorporated |
| R3-200292 | Introduction of LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| R3-200800 | Supporting LTE-Based 5G Terrestrial Broadcast | Ericsson GmbH, Eurolab |
| R3-200801 | Supporting LTE-Based 5G Terrestrial Broadcast | Ericsson GmbH, Eurolab |
| R3-200802 | Supporting LTE-Based 5G Terrestrial Broadcast | Ericsson GmbH, Eurolab |
| R3-200803 | Supporting LTE-Based 5G Terrestrial Broadcast | Ericsson GmbH, Eurolab |
| R3-200804 | Supporting LTE-Based 5G Terrestrial Broadcast | Ericsson GmbH, Eurolab |
| R3-200805 | Supporting LTE-Based 5G Terrestrial Broadcast | Ericsson GmbH, Eurolab |
| R3-200809 | M2AP Support for LTE-Based 5G Terrestrial Broadcast | Ericsson GmbH, Eurolab |
| R3-201137 | Summary of offline discussion for CB: # 34_Email034-eMBMS | Qualcomm |
| R3-201429 | Introduction of LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| 13.1 | General | |
| R3-200001 | DUMMY | ---- |
| R3-200016 | BL CR to 38.423: Support for IAB | Samsung |
| R3-200017 | BL CR to 38.463: Support for IAB | Huawei |
| R3-200018 | BL CR to 36.423: Support for IAB | Samsung |
| R3-200019 | BL CR to 38.425: Support for IAB | Samsung |
| R3-200020 | BL CR to 36.413: Support for IAB | Huawei |
| R3-200021 | draftCR TS 38.300 Mapping of Uplink Traffic to Backhaul RLC Channels | Ericsson |
| R3-200022 | BL CR to 38.401: Support for IAB | Huawei |
| R3-200023 | BL CR to 38.413: Support for IAB | Nokia, Nokia Shanghai Bell |
| R3-200024 | BL CR to 38.470: Support for IAB | Ericsson |
| R3-200025 | BL CR to 38.473: Support for IAB | Ericsson |
| R3-200246 | BL CR to 38.473: Support for IAB | Ericsson |
| R3-200414 | IAB workplan update | Qualcomm Incorporated |
| R3-201138 | Summary of offline discussion for CB: # 35_Email035-IAB_BL_CRs | Qualcomm |
| R3-201287 | BL CR to 38.401: Support for IAB | Huawei |
| R3-201382 | BL CR to 38.470: Support for IAB | Ericsson |
| R3-201460 | BL CR to 36.423: Support for IAB | Samsung |
| R3-201461 | BL CR to 38.401 Support for IAB | Huawei |
| R3-201462 | BL CR to 38.470: Support for IAB | Ericsson |
| R3-201463 | BL CR to 38.473: Support for IAB | Ericsson |
| R3-201494 | BL CR to 38.473: Support for IAB | Ericsson |
| 13.2.1.1 | IAB Node Integration | |
| R3-200464 | (TP for NR_IAB BL CR for TS 38.401): IAB node integration in SA mode | ZTE, Sanechips |
| R3-200599 | (TP for NR-IAB BL CR for TS 38.401) Protocol Stack to support IAB EN-DC | Nokia, Nokia Shanghai Bell |
| R3-200600 | (TP for NR-IAB BL CR for TS 38.401) IAB – Topology discovery during F1 Setup procedure | Nokia, Nokia Shanghai Bell |
| R3-200749 | (TP for NR_IAB BL CR for TS 38.401): Rethinking about the IAB topology discovery | Huawei |
| R3-200750 | Draft LS to RAN2 on the IAB topology discovery | Huawei |
| R3-200810 | (TP for NR-IAB BL CR for TS 38.473): DU-MT Collocation Indication | Ericsson |
| R3-201139 | Summary of offline discussion for CB: # 39_Email039-IAB_integration | Ericsson |
| R3-201356 | (TP for IAB BL CRs 38.401): IAB integration | Ericsson |
| 13.2.1.2 | Adaptation, QoS, Bearer Setup | |
| R3-200416 | Remaining F1AP mapping configurations for IAB | Qualcomm Incorporated |
| R3-200465 | Further consideration on bearer mapping configuration | ZTE, Sanechips |
| R3-200466 | Default BH RLC channel configuration | ZTE, Sanechips |
| R3-200467 | Further consideration on routing configuration | ZTE, Sanechips |
| R3-200468 | (TP for NR_IAB BL CR for TS 38.473): Bearer Mapping Configuration | ZTE, Sanechips |
| R3-200469 | (TP for NR_IAB BL CR for TS 38.473): Routing Configuration | ZTE, Sanechips |
| R3-200564 | (TP for NR-IAB BL CR for 38.470) Further clean-up for CP mapping | Samsung |
| R3-200565 | (TP for NR-IAB BL CR for 38.473) Further discussion on UL mapping configuration at accessing IAB node | Samsung |
| R3-200566 | (TP for NR-IAB BL CR for 38.473) Mapping configuration for intra-donor and intermediate IAB node | Samsung |
| R3-200567 | (TP for NR-IAB BL CR for 36.423) IP packet mapping for EN-DC case | Samsung |
| R3-200601 | (TP for NR-IAB BL CR for TS 38.473) Configure UL BAP Address in the Donor-DU | Nokia, Nokia Shanghai Bell |
| R3-200602 | (TP for NR-IAB BL CR for TS 38.473) UL CP mapping in IAB | Nokia, Nokia Shanghai Bell |
| R3-200603 | (TP for NR-IAB BL CR for TS 38.473) Bearer mapping configuration in Donor-DU and intermediate IAB nodes | Nokia, Nokia Shanghai Bell |
| R3-200604 | (TP for NR-IAB BL CR for TS 38.473) Update on Routing Configuration | Nokia, Nokia Shanghai Bell |
| R3-200605 | Support for IAB | Nokia, Nokia Shanghai Bell |
| R3-200751 | (TP for NR_IAB BL CR for TS38.473): BAP configuration for IAB donor DU | Huawei |
| R3-200752 | (TP for NR_IAB BL CR for TS38.473): Bearer mapping configuration for intermediate IAB nodes | Huawei |
| R3-200753 | (TP for NR_IAB BL CR for TS38.473): BAP configuration for F1-C and non-F1 traffic in access IAB node | Huawei |
| R3-200754 | (TP for NR-IAB BL CR for TS 38.473): Remaining issues for BH RLC channel management | Huawei |
| R3-200811 | (TP for NR-IAB BL CR for TS 38.473): Downlink Backhaul RLC Channel Mapping Configuration for IAB-nodes | Ericsson, KDDI |
| R3-200812 | (TP for NR-IAB BL CR for TS 38.473): Uplink Mapping of Non-UP Traffic at Access IAB-nodes | Ericsson, KDDI |
| R3-200813 | (TP for NR-IAB BL CR for TS 38.473): FFS Cleanup | Ericsson |
| R3-200814 | (TP for NR-IAB draftCR for TS 38.300): Uplink Traffic Mapping at Access IAB-node | Ericsson |
| R3-201140 | Summary of offline discussion for CB: # 41_Email041-IAB_Traffic_mapping | Ericsson |
| R3-201141 | Summary of offline discussion for CB: # 40_Email040-IAB_Cleanups | Samsung |
| R3-201142 | Summary of offline discussion for CB: # 43_Email043-IAB_Traffic_at_Donor_and_Intermediate_nodes | Nokia |
| R3-201211 | (TP for NR-IAB BL CR for TS 38.473): Uplink Mapping of Non-UP Traffic at Access IAB-nodes | Ericsson, KDDI |
| R3-201357 | (TP for IAB BL CRs 38.473): IAB Traffic mapping | Ericsson |
| R3-201375 | (TP for NR-IAB BL CR for TS 38.473): IAB Cleanups | Ericsson |
| R3-201379 | (TP for NR-IAB BL CR for 38.470) Further clean-up for CP mapping | Samsung |
| R3-201393 | (TP for NR_IAB BL CR for TS 38.473): Routing Configuration | ZTE, Sanechips |
| R3-201402 | (TP for NR-IAB BL CR for 38.470) Further clean-up for CP mapping | Samsung |
| R3-201415 | (TP for IAB BL CRs 38.473): IAB Traffic mapping | Ericsson |
| 13.2.1.3 | IP Address Management | |
| R3-200417 | Remaining IP transport issues for IAB | Qualcomm Incorporated |
| R3-200568 | (TP for NR-IAB BL CR for 38.473) Further discussion on IP address issues of IAB network | Samsung |
| R3-200569 | [Draft] LS on IP address management in IAB network | Samsung |
| R3-200606 | The impact to F1 interface regarding IAB IP address management | Nokia, Nokia Shanghai Bell |
| R3-200755 | (TP for NR-IAB BL CR for TS 38.473) :IP address management for IAB node | Huawei |
| R3-200770 | (TP for NR_IAB BL CR for TS 38.473): IP address allocation | ZTE, Sanechips |
| R3-200785 | Discussion on the F1AP signalling for IP address allocation | ZTE, Sanechips |
| R3-200815 | (TP for NR-IAB BL CR for TS 38.473): IP Address Allocation for IAB-nodes | Ericsson, KDDI |
| R3-201143 | Summary of offline discussion for CB: # 44_Email044-IAB_IPaddr_mgmt | Samsung |
| R3-201420 | LS on IP address management in IAB network | Samsung |
| 13.2.1.4 | IAB-Specific Physical Layer Parameter Handling in F1AP | |
| R3-200415 | (TP for NR_IAB BL CR to TS 38.473) F1AP - PHY layer configuration | Qualcomm Incorporated |
| R3-200759 | (TP for NR-IAB BL CR for TS 38.473) : Cell-specific signals/channels configuration of child IAB-DU | Huawei |
| R3-201144 | Summary of offline discussion for CB: # 45_Email045-IAB_PHYlayer_param_F1AP | Qualcomm |
| R3-201355 | (TP to NR_IAB BL CR to 38473) PHY layer parameter configuration | Qualcomm |
| 13.2.2.1 | Flow Control | |
| R3-200470 | Consideration on DL E2E flow control in IAB | ZTE, Sanechips |
| R3-200607 | Use of current DDDS for e2e flow control in IAB | Nokia, Nokia Shanghai Bell |
| R3-200757 | (TP for NR-IAB BL CR for TS 38.425) :E2E flow control for IAB Network | Huawei |
| R3-200816 | (TP for NR-IAB BL CR for TS 38.425): Downlink End-to-End Flow Control in IAB Networks | Ericsson |
| R3-200817 | General Principles of IAB Downlink End-to-End Flow Control | Ericsson |
| R3-201003 | (TP for NR-IAB BL CR for 38.425) Enhancement to DDDS for E2E flow control in IAB | BEIJING SAMSUNG TELECOM R&D |
| 13.2.4 | DC Operation with IAB | |
| R3-200471 | (TP for NR_IAB BL CR for TS 36.423): Support of F1AP signalling over LTE leg | ZTE, Sanechips |
| R3-200570 | (TP for NR-IAB BL CR for 36.423) Further discussion on F1AP over X2 | Samsung |
| R3-200608 | (TP for NR-IAB BL CR for TS 36.423) Transferring F1AP over X2 interface to support IAB EN-DC | Nokia, Nokia Shanghai Bell |
| R3-200758 | (TP for NR-IAB BL CR for TS36.423): Support of F1AP over LTE | Huawei |
| R3-200818 | On Multi-connectivity for IAB-nodes | Ericsson |
| R3-201145 | Summary of offline discussion for CB: # 47_Email047-IAB_DCoperation | ZTE |
| R3-201388 | (TP for NR_IAB BL CR for TS 36.423): Support of F1AP signalling over LTE leg | ZTE, Sanechips |
| R3-201425 | (TP for NR_IAB BL CR for TS 36.423): Support of F1AP signalling over LTE leg | ZTE, Sanechips |
| 13.3.1 | Routing Functionality | |
| R3-200760 | Remaining issues for routing in IAB network | Huawei |
| R3-201146 | Summary of offline discussion for CB: # 48_Email048-IAB_routing_AOB | Huawei |
| R3-201377 | [DRAFT] LS on the source IP configuration | Huawei |
| R3-201418 | LS on the inter donor DU re-routing and source IP configuration | Huawei |
| 13.3.2.1 | Functions and Criteria | |
| R3-200319 | Considerations on Intra-CU topology adaptation procedure | KDDI Corporation |
| R3-200418 | (TP for NR_IAB BL CR to TS 38.401) BH RLF recovery | Qualcomm Incorporated |
| R3-200571 | (TP for NR-IAB BL CR for 38.401) IAB node reestablishment | Samsung |
| R3-200637 | (TP for NR-IAB BL CR for TS 38.473): F1AP signaling to indicate IAB node congestion | AT&T |
| R3-200756 | CP based E2E flow control for IAB | Huawei |
| R3-200761 | (TP for NR_IAB BL CR for TS 38.401): Backhaul RLF Recovery | Huawei |
| R3-201147 | Summary of offline discussion for CB: # 49_Email049-IAB_migration_criteria | Qualcomm |
| R3-201363 | (TP to NR_IAB BL CR to 38401) BH RLF recovery procedure | Qualcomm |
| 13.3.2.2 | Under the Same Donor | |
| R3-200301 | (TP for NR BL CR for TS 38.401) Clean-up for Intra-CU topology adaption procedure | CATT |
| R3-200315 | Open issue on IAB-node migration under the same IAB-donor | LG Electronics |
| R3-200316 | (TP for NR_IAB BL CR for TS 38.401): Open issue on IAB-node migration under the same IAB-donor | LG Electronics |
| R3-200419 | (TP for NR_IAB BL CR to TS 38.401) Topology Adaptation | Qualcomm Incorporated |
| R3-200472 | Discussion on network-controlled IAB migrating handling | ZTE, Sanechips |
| R3-200473 | (TP for NR_IAB BL CR for TS 38.401): Intra-CU topology adaptation Procedure | ZTE, Sanechips |
| R3-200563 | (TP for NR-IAB BL CR for 38.401) IAB Stage 2 clean up | Samsung |
| R3-200762 | (TP for NR_IAB BL CR for TS 38.401): Intra IAB donor-CU topology adaptation procedure | Huawei |
| R3-200819 | (TP for NR-IAB BL CR for TS 38.401): Remaining Issues | Ericsson, KDDI |
| R3-201148 | Summary of offline discussion for CB: # 50_Email050-IAB_migration_same_donor | CATT |
| R3-201332 | (TP for NR BL CR for TS 38.401) Clean-up on Intra-CU topology adaption | CATT |
| R3-201419 | (TP for NR BL CR for TS 38.401) Clean-up on Intra-CU topology adaption | CATT |
| 13.3.2.3 | Between Donors | |
| R3-200763 | Inter IAB donor CU topology adaptation | Huawei |
| 14.1 | General | |
| R3-200026 | Introduction of NBIOT dedicated CP functions when connected to 5GC | Nokia, Nokia Shanghai Bell |
| R3-200027 | Introduction of Suspend-Resume for 5GC | Nokia, Nokia Shanghai Bell |
| R3-200028 | Introduction of CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC (Stage 2) | LG Electronics |
| R3-200029 | Introduction of NB-IoT Paging and eDRX aspects | Ericsson, Huawei, Qualcomm Incorporated |
| R3-200030 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-200031 | Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC | Qualcomm Incorporated |
| R3-200032 | Introduction of CP UP NB-IoT Others | Huawei |
| R3-200033 | Common CP/UP aspects of CIoT UEs when connected to 5GC | Ericsson, ZTE |
| R3-200034 | Introduction of Suspend-Resume for 5GC (UP common part) | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-200035 | Introduction of NB-IoT related NG-AP procedures | Huawei |
| R3-200036 | Introduction of CP UP NB-IoT Others | Huawei |
| R3-200037 | Introduction of MT Early Data Transmission | Qualcomm Incorporated, Huawei, Ericsson |
| R3-200038 | Introduction of eMTC connected to 5GC | ZTE, Ericsson, Huawei, LG |
| R3-200231 | (TP for BL CR 38.413 on Suspend Resume) Rapporteur correction to BL CR Supend-Resume for TS 38.413 | Nokia, Nokia Shanghai Bell |
| R3-200247 | Introduction of CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC (Stage 2) | LG Electronics |
| R3-201149 | Summary of offline discussion for CB: # 61_Email061-MTC_NB-IoT_BLs | Huawei |
| R3-201446 | Introduction of MT Early Data Transmission | Qualcomm Incorporated, Huawei, Ericsson |
| R3-201447 | Introduction of eMTC connected to 5GC | ZTE, Ericsson, Huawei, LG |
| R3-201485 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| 14.2 | Support for Mobile-Terminated Early Data Transmission | |
| R3-200233 | (TP for BL CR 36.413 on MT EDT) Finalization of MT EDT | Nokia, Nokia Shanghai Bell |
| R3-200422 | (TP to BL CR#1682 / 36.413 on MT-EDT) MT-EDT Open Issues | Qualcomm Incorporated |
| R3-201150 | Summary of offline discussion for CB: # 60bis_Email036-MTC_NB-IoT_MT-EDT_finalization | Nokia |
| R3-201266 | (TP for BL CR 36.413 on MT EDT) Finalization of MT EDT | Nokia, Nokia Shanghai Bell |
| 14.3.1 | LTE-M Identification in 5GC | |
| R3-200234 | (TP for BL CR172 38.413 on eMTC connected to 5GC) Identification and LTE-M Mobility in 5GC | Nokia, Nokia Shanghai Bell |
| R3-200289 | Remaining issues on LTE-M in RAN3 specifications | Qualcomm Incorporated |
| R3-201044 | Finalizing discussion on LTE-M indicator in NGAP | Ericsson |
| R3-201151 | Summary of offline discussion for CB: # 61bis_Email061bis-MTC_NB-IoT_LTE-M_finalization | Qualcomm |
| 14.3.2 | Others | |
| R3-200181 | (TP to BL CR#0172 “Introduction of eMTC connected to 5GC” for TS38.413) Paging aspects for RRC_INACTIVE state | Huawei |
| R3-200182 | Introduction of eMTC connected to 5GC | Huawei |
| R3-200183 | (TP to BL CR#0153 “Common CP/UP aspects of CIoT UEs when connected to 5GC” for TS38.413) Support of Coverage Enhancement | Huawei, Ericsson |
| R3-200184 | (TP to BL CR#0157 “Introduction of CP UP NB-IoT Others” for TS 38.413) Overload Action | Huawei |
| R3-200185 | (TP to BL CR#0156 “Introduction of NB-IoT related NG-AP procedures” for TS 38.413) 5G-S-TMSI in Error Indication | Huawei |
| R3-200232 | (TP for BL CR 38.423 on Suspend Resume) Rapporteur Correction to BL CR Suspend Resume for TS 38.423 | Nokia, Nokia Shanghai Bell |
| R3-200264 | (TP to BL CR #0188 Introduction of Suspend-Resume for 5GC (UP common part) for TS38.413): Delete the UE CONTEXT SUSPEND FAILURE procedure | ZTE |
| R3-200265 | (TP to BL CR#0120 Introduction of NB-IoT Paging and eDRX aspects for TS38.413): Removal of NB-IoT UE Identity Index IE | ZTE, Huawei |
| R3-200266 | Consideration on Core Network awareness of D-PUR configuration | ZTE |
| R3-200267 | CR38.413 for support of AMF awareness of D-PUR configuration for connection to 5GC | ZTE |
| R3-200268 | CR36.413 for support of MME awareness of D-PUR configuration | ZTE |
| R3-200363 | (TP for BL CR173 for 38.413 on CP CIoT common NBIOT/MTC) Correction of Connection Establishment Indication | Nokia, Nokia Shanghai Bell |
| R3-200423 | (TP to BL CR#0188 / 38.413 on Suspend-Resume) Introduction of immediate transition to suspension | Qualcomm Incorporated |
| R3-200790 | Discussion on support of early data transmission in 5GS | LG Electronics |
| R3-200791 | TP to BL CR#0188 “Introduction of Suspend-Resume for 5GC (UP common part)” for TS 38.413: Support of MO-EDT for UP CIoT 5GS optimization | LG Electronics |
| R3-200792 | TP to BL CR#0182 “Introduction of Suspend-Resume” for TS 38.423: UE identifier for UP CIoT 5GS Optimisation | LG Electronics |
| R3-201009 | Introduction of Pending data indication and UE subscription-based differentiation to support CIoT connected to 5GC | Ericsson |
| R3-201010 | Removal of Connection Establishment Indication | Ericsson |
| R3-201011 | Discussion on UE-specific DRX for NB-IoT | Ericsson |
| R3-201012 | TP to BL CR#0120 for TS 38.413: introduction of NB-IoT UE specific DRX | Ericsson |
| 14.4.1 | RLF | |
| R3-200186 | Consideration on RLF in NB-IoT | Huawei, CMCC |
| R3-200187 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC |
| R3-200188 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC |
| R3-201152 | Summary of offline discussion for CB: # 70_Email070-MTC_NB-IoT_SON_RLF | Huawei |
| R3-201269 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC, Ericsson |
| R3-201270 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC, Ericsson |
| 14.4.2 | PRACH Configuration Exchange | |
| R3-200269 | Consideration on NB-IoT PRACH optimization | ZTE, Ericsson |
| R3-200270 | CR for 36.423 on NB-IoT PRACH configuration exchange over X2AP | ZTE, Ericsson, Huawei |
| R3-200271 | CR for 38.423 on NB-IoT PRACH configuration exchange over XnAP | ZTE, Huawei |
| R3-201153 | Summary of offline discussion for CB: # 71_Email071-MTC_NB-IoT_SON_PRACHconfig_xch | ZTE |
| 14.4.3 | ANR | |
| R3-200189 | Consideration on NB-IoT ANR report | Huawei |
| R3-200190 | Introduction of NB-IoT ANR report | Huawei |
| R3-200272 | Consideration on NB-IoT ANR Report Exchange | ZTE |
| R3-200312 | Introduction of NB-IoT ANR report | Huawei |
| R3-201013 | Considerations on SON support for reporting | Ericsson |
| R3-201154 | Summary of offline discussion for CB: # 72_Email072-MTC_NB-IoT_SON_ANR | ZTE |
| 14.5.1 | Group WUS | |
| R3-200191 | Consideration on UE group wake up signal (WUS) | Huawei, Vodafone |
| R3-200192 | Support of WUS Group | Huawei, Vodafone |
| R3-200193 | [Draft]Reply LS on assistance indication for WUS | Huawei |
| R3-200273 | CR36.413 for Support of WUS assistance information transfer | ZTE |
| R3-201014 | Introduction of WUS grouping | Ericsson, ZTE |
| R3-201015 | Introduction of WUS grouping | Ericsson |
| 15.1 | General | |
| R3-200039 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation, CATT, ZTE, Huawei |
| R3-200040 | Baseline CR for introducing Rel-16 NR mobility enhancement | Ericsson |
| R3-200041 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation |
| R3-200042 | Baseline CR for introducing Rel-16 LTE further mobility enhancement | Intel Corporation |
| R3-200043 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-200044 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-200045 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-200046 | Baseline CR for introducing Rel-16 NR mobility enhancement | Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-201102 | Revised Work Plan for LTE/NR Mobility WIs | Intel Corporation |
| R3-201155 | Summary of offline discussion for CB: # 82bis_Email042-MobEnhs_BLs | Intel |
| R3-201298 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-201448 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation |
| R3-201449 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-201450 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-201451 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation, CATT, ZTE, Huawei |
| R3-201452 | Baseline CR for introducing Rel-16 NR mobility enhancement | Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-201453 | Baseline CR for introducing Rel-16 NR mobility enhancement | Ericsson, CATT |
| 15.2.1 | Common | |
| R3-200522 | Handover Preparation Procedures for DAPS HO | CATT |
| R3-200523 | (TP for [LTE_feMob] BL CR for TS 36413)Handover Preparation Procedure for DAPS HO | CATT |
| R3-200524 | (TP for [NR_Mob_enh] BL CR for TS 38413)Handover Preparation Procedure for DAPS HO | CATT |
| R3-200525 | (TP for [LTE_feMob] BL CR for TS 36423)Handover Preparation Procedure for DAPS HO | CATT |
| R3-200526 | (TP for [NR_Mob_enh] BL CR for TS 38423)Handover Preparation Procedure for DAPS HO | CATT |
| R3-201072 | DAPS HO - per-DRB Handover Preparation | Ericsson |
| R3-201073 | (TP for NR Mob BL CR for TS 38.423): DAPS HO - per-DRB Handover Preparation | Ericsson |
| R3-201074 | (TP for LTE_feMob BL CR for TS 36.423): DAPS HO - per-DRB Handover Preparation | Ericsson |
| R3-201075 | Support of S1 and NG DAPS HO | Ericsson |
| R3-201103 | (TP for LTE_feMob-Core BL CR for TS 36.300): Support for per DRB DAPS | Intel Corporation |
| R3-201104 | (TP for LTE_feMob-Core BL CR for TS 36.423): Support for per DRB DAPS | Intel Corporation |
| R3-201105 | (TP for NR_Mob_enh-Core BL CR for TS 38.300): Support for per DRB DAPS | Intel Corporation |
| R3-201106 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): Support for per DRB DAPS | Intel Corporation |
| R3-201107 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Support for per DRB DAPS | Intel Corporation |
| R3-201108 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): Support for per DRB DAPS | Intel Corporation |
| R3-201156 | Summary of offline discussion for CB: # 83_Email043-MobEnh_DAPS_common | CATT |
| R3-201308 | (TP for LTE_feMob-Core BL CR for TS 36.300): Support for per DRB DAPS | Intel Corporation |
| R3-201309 | (TP for NR_Mob_enh-Core BL CR for TS 38.300): Support for per DRB DAPS | Intel Corporation |
| R3-201310 | (TP for [LTE_feMob] BL CR for TS 36413)Handover Preparation Procedure for DAPS HO | CATT |
| R3-201311 | (TP for [NR_Mob_enh] BL CR for TS 38413)Handover Preparation Procedure for DAPS HO | CATT |
| R3-201312 | (TP for [LTE_feMob] BL CR for TS 36423)Handover Preparation Procedure for DAPS HO | CATT |
| R3-201313 | (TP for [NR_Mob_enh] BL CR for TS 38423)Handover Preparation Procedure for DAPS HO | CATT |
| R3-201421 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | CATT, Nokia, Nokia Shanghai Bell |
| R3-201422 | Baseline CR for introducing Rel-16 NR mobility enhancement | CATT, Nokia, Nokia Shanghai Bell |
| 15.2.2 | E-UTRAN | |
| R3-200503 | (TP for LTE_feMob BL CR for TS 36.423): Correction to DAPS HO Indication | Huawei |
| 15.2.3 | NR | |
| R3-200410 | SN initiated SN change | Qualcomm Incorporated |
| R3-200411 | Data forwarding in DAPS HO with QoS flow remapping | Qualcomm Incorporated |
| R3-200413 | Per DRB eMBB HO | Qualcomm Incorporated |
| R3-200527 | CR to TS 38.463 for E1 impact during DAPS Handover | CATT |
| 15.3.1 | Common | |
| R3-201109 | Wrap-up for CHO | Intel Corporation |
| R3-201110 | (TP for LTE_feMob-Core BL CR for TS 36.300): Clean-up for Stage-2 CHO | Intel Corporation |
| R3-201111 | (TP for NR_Mob_enh-Core BL CR for TS 38.300): Clean-up for Stage-2 CHO | Intel Corporation |
| R3-201157 | Summary of offline discussion for CB: # 86_Email086-MobEnh_CHO_common_cleanup | Intel |
| 15.3.1.1 | Conditional PSCell Change | |
| R3-200320 | Further Discussion on Candidate Target PScell&SCG Cancel without MN&SN Change | ZTE |
| R3-200321 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | ZTE, CATT, NTT DOCOMO, INC. |
| R3-200528 | (TP for [NR_Mob_enh] BL CR for TS 38.473)CPAC-F1 impact | CATT |
| R3-200765 | (TP for NR_Mob_enh BL CR for TS 38.473) Introducing Intra-SN change | Google Inc. |
| R3-201158 | Summary of offline discussion for CB: # 87_Email087-MobEnh_CHO_common_condPSCellchg | ZTE |
| R3-201282 | (TP for NR_Mob_enh BL CR for TS 38.473) Introducing Intra-SN change | Google Inc. |
| R3-201303 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | ZTE, CATT, NTT DOCOMO, INC., Google, China Telecom |
| 15.3.1.2 | CHO Preparation | |
| R3-200504 | Remaining FFSs for CHO | Huawei |
| R3-200505 | (TP for NR_Mob_enh BL CR for TS 38.423): Remaining FFSs for CHO | Huawei |
| R3-200506 | (TP for LTE_feMob BL CR for TS 36.423): Remaining FFSs for CHO | Huawei |
| R3-200529 | Further Consideration on CHO preparation Procedure | CATT |
| R3-200530 | (TP for [LTE_feMob] BL CR for TS 36423)Further Consideration on CHO Preparation Procedure | CATT |
| R3-200531 | (TP for [NR_Mob_enh] BL CR for TS 38423)Further Consideration on CHO Preparation Procedure | CATT |
| R3-200677 | Clarification of UE X2AP/XnAP ID for multiple transactions in Conditional Handover | Samsung Electronics |
| R3-200679 | (TP for LTE_feMob BL CR for TS 36.423) Clarification of new UE X2AP ID for multiple transactions in Conditional Handover | Samsung Electronics |
| R3-200680 | (TP for NR_Mob BL CR for TS 38.423) Clarification of target UE XnAP ID for multiple transactions in Conditional Handover | Samsung Electronics |
| R3-201076 | CHO - Remaining stage-3 issues | Ericsson |
| R3-201077 | (TP for NR Mob BL CR for TS 38.423): CHO - Remaining stage-3 issues | Ericsson |
| R3-201078 | (TP for LTE_feMob BL CR for TS 36.423): CHO - Remaining stage-3 issues | Ericsson |
| R3-201087 | Consideration on FFSs for support of CHO | LG Electronics |
| R3-201159 | Summary of offline discussion for CB: # 88_Email088-MobEnh_CHO_common_CHOprep | Ericsson |
| R3-201384 | (TP for NR_Mob_enh BL CR for TS 38.300): Introduction of Immediate Handover definition | Ericsson |
| R3-201385 | (TP for LTE_feMob BL CR for TS 36.300): Introduction of Immediate Handover definition | Ericsson |
| 15.3.1.3 | CHO Modification | |
| R3-200161 | Discussion on Conditional Handover Modification procedure | China Telecommunication |
| R3-200213 | Avoiding unnecessary CHO modification | Nokia, Nokia Shanghai Bell |
| R3-200214 | (TP for NR_Mob_enh BL CR for TS 38.423): Enabling information on the scope of changes allowed for the source | Nokia, Nokia Shanghai Bell |
| R3-200215 | (TP for LTE_feMob BL CR for TS 36.423): Enabling information on the scope of changes allowed for the source | Nokia, Nokia Shanghai Bell |
| R3-200322 | TP for LTE_Mob_enh BL CR for TS 36.423 “CHO-replace” code and target node UE APID are not needed | ZTE |
| R3-200323 | TP for NR_Mob_enh BL CR for TS 38.423 “CHO-replace” code and target node UE APID are not needed | ZTE |
| R3-200507 | Target Node Initiated CHO Modification | Huawei |
| R3-200508 | (TP for NR_Mob_enh BL CR for TS 38.423): Target Node Initiated CHO Modification | Huawei |
| R3-200509 | (TP for LTE_feMob BL CR for TS 36.423): Target Node Initiated CHO Modification | Huawei |
| R3-201079 | CHO - Modification from target node | Ericsson |
| R3-201080 | (TP for NR Mob BL CR for TS 38.423): CHO - Modification from target node | Ericsson |
| R3-201081 | (TP for LTE_feMob BL CR for TS 36.423): CHO - Modification from target node | Ericsson |
| R3-201160 | Summary of offline discussion for CB: # 89_Email088-MobEnh_CHO_common_CHOmod | Huawei |
| 15.3.1.4 | CHO Cancellation | |
| R3-200216 | Issues with target-initiated cancellation for CHO | Nokia, Nokia Shanghai Bell |
| R3-200217 | (TP for NR_Mob_enh BL CR for TS 38.423): Correction of the target-initiated cancellation for CHO | Nokia, Nokia Shanghai Bell |
| R3-200218 | (TP for LTE_feMob BL CR for TS 36.423): Correction of the target-initiated cancellation for CHO | Nokia, Nokia Shanghai Bell |
| R3-200331 | TP for LTE_Mob_enh BL CR for TS 36.423 Correction of Conditional HO Cancel | ZTE |
| R3-200333 | TP for NR_Mob_enh BL CR for TS 38.423 Correction of Conditional HO Cancel | ZTE |
| R3-201161 | Summary of offline discussion for CB: # 90_Email090-MobEnh_CHO_common_CHOcancel | Nokia |
| R3-201304 | TP for LTE_Mob_enh BL CR for TS 36.423 Correction of Conditional HO Cancel | ZTE |
| R3-201305 | TP for NR_Mob_enh BL CR for TS 38.423 Correction of Conditional HO Cancel | ZTE |
| 15.3.1.5 | Overload Issues | |
| R3-200219 | Solutions to avoid overload due to CHO | Nokia, Nokia Shanghai Bell, Vodafone, British Telecom |
| R3-200220 | (TP for NR_Mob_enh BL CR for TS 38.423): Information on CHO triggering | Nokia, Nokia Shanghai Bell, Vodafone, British Telecom |
| R3-200221 | (TP for LTE_feMob BL CR for TS 36.423): Information on CHO triggering | Nokia, Nokia Shanghai Bell, Vodafone, British Telecom |
| R3-201162 | Summary of offline discussion for CB: # 91_Email091-MobEnh_CHO_common_overload | Nokia |
| R3-201358 | (TP for NR_Mob_enh BL CR for TS 38.423): Information on CHO triggering | Nokia, Nokia Shanghai Bell, Vodafone, British Telecom |
| R3-201359 | (TP for LTE_feMob BL CR for TS 36.423): Information on CHO triggering | Nokia, Nokia Shanghai Bell, Vodafone, British Telecom |
| 15.3.3 | NR | |
| R3-200343 | Further Discussion of CHO Modify and Cancel of Candidate Target Cells over F1AP | ZTE, China Telecom, China Unicom |
| R3-200399 | TP for NR_Mob_enh BL CR for TS 38.473 Introduction of CHO Modify and Cancel of Candidate Target Cells | ZTE, China Telecom, China Unicom |
| R3-200400 | TS38.470 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| R3-200520 | Further Discussion of CHO Addition, Modify and Cancel of Upper Layer UP Resources over E1AP | ZTE, China Telecom, China Unicom |
| R3-200521 | TS38.463 Introduction of CHO Addition, Modify and Cancel of Upper Layer UP Resources | ZTE, China Telecom, China Unicom |
| R3-200532 | CR to TS 38.463 for E1 impact during Conditional Handover | CATT |
| R3-200549 | TS38.460 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| R3-200764 | (TP for NR_Mob_enh BL CR for TS 38.401) Introducing conditional mobility | Google Inc. |
| R3-201163 | Summary of offline discussion for CB: # 92_Email092-MobEnh_CHO_NR | ZTE |
| R3-201281 | (TP for NR_Mob_enh BL CR for TS 38.401) Introducing conditional mobility | Google Inc. |
| R3-201361 | (TP for NR_Mob_enh-Core BL CR for TS 38.473): Support for CHO | Intel Corporation, ZTE, Google |
| R3-201423 | (TP for NR_Mob_enh BL CR for TS 38.401) Introducing conditional mobility | Google, ZTE, Intel |
| R3-201424 | (TP for NR_Mob_enh-Core BL CR for TS 38.473): Support for CHO | Intel Corporation, ZTE, Google |
| 15.4.1 | Common | |
| R3-200766 | (TP for NR_Mob_enh BL CR for TS 38.401) Corrections to DAPS HO | Google Inc. |
| R3-201112 | (TP for LTE_feMob-Core BL CR for TS 36.423): Early Forwarding support for DAPS/CHO | Intel Corporation |
| R3-201113 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): Early Forwarding support for DAPS/CHO | Intel Corporation |
| R3-201114 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): Early Forwarding support for DAPS/CHO | Intel Corporation |
| R3-201115 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Early Forwarding support for DAPS/CHO | Intel Corporation |
| R3-201164 | Summary of offline discussion for CB: # 93_Email093-MobEnh_datafwd_common | Intel |
| R3-201339 | (TP for LTE_feMob-Core BL CR for TS 36.423): Early Forwarding support for DAPS/CHO | Intel Corporation |
| R3-201340 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): Early Forwarding support for DAPS/CHO | Intel Corporation |
| R3-201341 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): Early Forwarding support for DAPS/CHO | Intel Corporation |
| R3-201342 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Early Forwarding support for DAPS/CHO | Intel Corporation, Google |
| R3-201387 | (TP for LTE_feMob-Core BL CR for TS 36.423): Early Forwarding support for DAPS/CHO | Intel Corporation |
| 15.4.1.1 | Handover Interruption Reduction | |
| R3-200510 | (TP for NR_Mob_enh BL CR for TS 38.300): Early forwarding transfer for DAPS handover | Huawei |
| R3-200511 | (TP for LTE_feMob BL CR for TS 36.300): Early forwarding transfer for DAPS handover | Huawei |
| R3-200512 | (TP for NR_Mob_enh BL CR for TS 38.423): Early forwarding transfer for DAPS handover | Huawei |
| R3-200513 | (TP for LTE_feMob BL CR for TS 36.423): Early forwarding transfer for DAPS handover | Huawei |
| R3-200533 | Further Consideration on SN Status Transfer Procedure for DAPS | CATT |
| R3-200534 | (TP for [LTE_feMob] BL CR for TS 36423)SN Status Transfer Procedure for DAPS | CATT |
| R3-200535 | (TP for [NR_Mob_enh] BL CR for TS 38423)SN Status Transfer Procedure for DAPS | CATT |
| 15.4.1.2 | CHO | |
| R3-200162 | Discussion on early data forwarding for Conditional Handover | China Telecommunication |
| R3-200550 | TP for LTE_Mob_enh BL CR for TS 36.423 Correction of CHO Per Target Cell TEID | ZTE |
| R3-200551 | TP for NR_Mob_enh BL CR for TS 38.423 Correction of CHO Per Target Cell TEID | ZTE |
| R3-200681 | Data forwarding configuration in parallel transactions to multiple target cells in the same target node | Samsung Electronics |
| R3-200682 | (TP for LTE_feMob BL CR for TS 36.300) Clarification of data forwarding in parallel transaction for Conditional Handover | Samsung Electronics |
| R3-200684 | (TP for NR_Mob BL CR for TS 38..300) Clarification of data forwarding in parallel transaction for Conditional Handover | Samsung Electronics |
| R3-201034 | On Early Data Forwarding for CHO | Apple Inc. |
| R3-201165 | Summary of offline discussion for CB: # 95_Email095-MobEnh_datafwd_CHO | China Telecom |
| R3-201306 | TP for LTE_Mob_enh BL CR for TS 36.423 Correction of CHO Per Target Cell TEID | ZTE |
| R3-201307 | TP for NR_Mob_enh BL CR for TS 38.423 Correction of CHO Per Target Cell TEID | ZTE |
| 15.4.3 | NR | |
| R3-200412 | Remaining issues in data forwarding | Qualcomm Incorporated |
| R3-200703 | E1 impact to support data forwading in DAPS Handover and Conditional Handover | Samsung Electronics |
| R3-200705 | E1 impact to support data forwarding in DAPS Handover and Conditional Handover | Samsung Electronics |
| R3-201082 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| R3-201083 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| R3-201085 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| 16.1 | General | |
| R3-200047 | BL CR NPN for 38.401 | China Telecommunication |
| R3-200048 | Introduction of NPN | Huawei, China Telecom |
| R3-200049 | Introduction of Non-Public Networks for TS38.463 | ZTE Corporation |
| R3-200050 | Introduction of Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-200051 | Introduction of Non-Public Networks | Qualcomm Incorporated |
| R3-200052 | Introduction of Non-Public Networks | Ericsson |
| R3-200152 | Introduction of Non Public Networks in E-UTRA connected to 5GC | VODAFONE Group Plc |
| R3-200154 | Updated work plan for PRN WI | China Telecommunication |
| R3-200155 | TP for NPN BL CR for 38.401 | China Telecommunication, Nokia, Nokia Shanghai Bell, Huawei |
| R3-200170 | Information on RAN2 BL CR | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-201166 | Summary of offline discussion for CB: # 72bis_Email072bis-NPN_BLs | China Telecom |
| R3-201336 | Introduction of Non-Public Networks | Qualcomm Incorporated |
| R3-201348 | TP for NPN BL CR for 38.401 | China Telecommunication, Nokia, Nokia Shanghai Bell, Huawei |
| R3-201454 | Introduction of Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-201455 | BL CR NPN for 38.401 | China Telecommunication |
| R3-201456 | Introduction of Non-Public Networks | Qualcomm Incorporated |
| R3-201457 | Introduction of Non-Public Networks | Ericsson |
| R3-201458 | Introduction of Non-Public Networks for TS38.463 | ZTE |
| R3-201459 | Introduction of NPN | Huawei, China Telecom |
| 16.2.1 | Configuration Aspects over NG | |
| R3-200160 | TP for Configuration Aspects over NG interface | China Telecommunication |
| R3-200194 | (TP for NPN BL CR 38.413) Correction of NPN NG Configuration | Nokia, Nokia Shanghai Bell |
| R3-200196 | (TP for NPN BL CR 38.413) Support of CAG Configuration | Nokia, Nokia Shanghai Bell |
| R3-200353 | On UE Mobility in RRC Inactive for NPN | NEC |
| R3-200354 | (TP for NPN BL CR for 38.413) On UE Mobility in RRC Inactive for NPN | NEC |
| R3-200355 | (TP for NPN BL CR for 38.423) On UE Mobility in RRC Inactive for NPN | NEC |
| R3-200420 | (TP for CR#0290 to TS38.413 Baseline CR on NPN) Resolving open issues for NPN | Qualcomm Incorporated |
| R3-200710 | (TP for NPN BL CR for TS 38.413): Configuration aspects over NG | Huawei |
| R3-200711 | (TP for NPN BL CR for TS 38.300): Configuration aspects over NG | Huawei |
| R3-201167 | Summary of offline discussion for CB: # 73_Email073-NPN_NGconfig | Nokia |
| R3-201246 | (TP for NPN Baseline CR 38.300) Correction of NPN configuration | Nokia |
| R3-201268 | (TP for CR#0290 to TS38.413 Baseline CR on NPN) Resolving open issues for NPN | Qualcomm Incorporated |
| 16.2.2.1 | Initial UE Message | |
| R3-200197 | (TP for NPN BL CR for 38.300) Correction of NPN Access control | Nokia, Nokia Shanghai Bell |
| R3-200198 | (TP for NPN BL CR for 38.413) Correction of NPN Access control | Nokia, Nokia Shanghai Bell |
| R3-200337 | TP for CAG Subscription Expiry to TS38.413 | ZTE Corporation |
| R3-200356 | Discussion on Access Control in NPN | NEC |
| R3-200357 | (TP for NPN BL CR for 38.300) On Access Control in NPN | NEC |
| R3-200358 | (TP for NPN BL CR for 38.413) On Access Control in NPN | NEC |
| R3-200712 | (TP for NPN BL CR for TS 38.413): Initial UE message for NPN | Huawei |
| R3-200713 | (TP for NPN BL CR for TS 38.300): Access control for NPN | Huawei |
| R3-200793 | Discussion on initial access procedure in PNI-NPN | LG Electronics |
| R3-200794 | (TP for NPN BL CR for TS 38.413): Semantics description of NPN Access Information in Initial UE Message | LG Electronics |
| R3-200900 | NPN – On Access Control at Initial UE message | Ericsson |
| R3-200969 | NPN – On Access Control at Initial UE message | Ericsson |
| R3-201168 | Summary of offline discussion for CB: # 74_Email074-NPN_InitialUEmessage | Nokia |
| R3-201230 | (TP for NPN BL CR for 38.300) Correction of NPN Access control | Nokia, Nokia Shanghai Bell |
| R3-201231 | (TP for NPN BL CR for 38.413) Correction of NPN Access control | Nokia, Nokia Shanghai Bell |
| 16.2.2.2 | Mobility Restriction List | |
| R3-200714 | (TP for NPN BL CR for TS 38.413): Mobility restriction list | Huawei |
| R3-201169 | Summary of offline discussion for CB: # 75_Email075-NPN_MRL | Huawei |
| R3-201288 | (TP for NPN BL CR for TS 38.413): Mobility restriction list | Huawei |
| 16.2.3 | Mobility | |
| R3-200158 | Discussion on mobility of NPN | China Telecommunication |
| R3-200199 | (TP for NPN BL CR for 38.413) Correction of NPN Mobility | Nokia, Nokia Shanghai Bell |
| R3-200200 | (TP for NPN BL CR for 38.423) Correction of NPN Mobility | Nokia, Nokia Shanghai Bell |
| R3-200338 | Consideration on selected CAG ID | ZTE Corporation |
| R3-200446 | Discussion on NPN manual network selection | CATT |
| R3-200514 | (TP for NPN BL CR for 38.423) RRC resumption or reestablishment impact in NPN | BEIJING SAMSUNG TELECOM R&D |
| R3-200597 | Left issues on mobility for PNI-NPN | CMCC |
| R3-200715 | (TP for NPN BL CR for TS 38.300): Connected mobility for NPN | Huawei |
| R3-200716 | (TP for NPN BL CR for TS 38.423): Connected mobility for NPN | Huawei |
| R3-200795 | Clarification on mobility of NPN | LG Electronics |
| R3-201090 | [draft]LS to SA2 on NPN manual CAG selection | CATT |
| R3-201170 | Summary of offline discussion for CB: # 76_Email076-NPNmobility | Nokia |
| 16.2.4 | Paging | |
| R3-200717 | (TP for NPN BL CR for TS 38.413): RAN paging for inactive NPN UE | Huawei |
| R3-200718 | (TP for NPN BL CR for TS 38.300): RAN paging for inactive NPN UE | Huawei |
| R3-201171 | Summary of offline discussion for CB: # 77_Email077-NPNpaging | Huawei |
| 16.2.5 | Self-Configuration Aspects | |
| R3-200157 | On Self-configuration aspects for NPN | China Telecommunication |
| R3-200201 | (TP for NPN BL CR for 38.300) Correction of NPN self-configuration | Nokia, Nokia Shanghai Bell |
| R3-200719 | (TP for NPN BL CR for TS 38.423): Self-configuration aspect for NPN | Huawei |
| R3-200901 | [TP for BL CR 38.423] Proposal to resolve some open items in the BL CR | Ericsson |
| R3-200970 | [TP for BL CR 38.423] Proposal to resolve some open items in the BL CR | Ericsson |
| R3-201172 | Summary of offline discussion for CB: # 78_Email078-NPN_self_config | Ericsson |
| R3-201335 | [TP for BL CR 38.423] Proposal to resolve some open items in the BL CR | Ericsson |
| 16.2.6 | F1 Aspects | |
| R3-200156 | On F1 aspects for NPN | China Telecommunication |
| R3-200238 | (TP for NPN BL CR for TS 38.473): NPN for F1 | Nokia, Nokia Shanghai Bell |
| R3-200339 | Impact of NPN on F1 | ZTE Corporation |
| R3-200340 | TP for NPN support to TS38.473 | ZTE Corporation |
| R3-200421 | Requirements of NPN support on F1, E1 and Dual Connectivity | Qualcomm Incorporated |
| R3-200720 | (TP for NPN BL CR for TS 38.473): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-200721 | CR to TS 38.470 on support of NPN | Huawei, China Telecommunication |
| R3-200902 | NPN – F1 Aspects | Ericsson |
| R3-200903 | [TP for BL CR 38.473] Introduction of NPN F1AP content | Ericsson |
| R3-200971 | NPN – F1 Aspects | Ericsson |
| R3-200972 | [TP for BL CR 38.473] Introduction of NPN F1AP content | Ericsson |
| R3-201173 | Summary of offline discussion for CB: # 79_Email079-NPN_F1 | Huawei |
| R3-201286 | [Draft] LS on Network Slice Availability for NPNs | Ericsson |
| R3-201364 | CR to TS 38.470 on support of NPN | Huawei, China Telecom |
| R3-201365 | (TP for NPN BL CR for TS 38.473): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-201412 | [Draft] LS on Network Slice Availability for NPNs | Ericsson |
| 16.2.7 | E1 Aspects | |
| R3-200239 | (TP for NPN BL CR for TS 38.463): NPN for E1 | Nokia, Nokia Shanghai Bell |
| R3-200341 | TP to capture agreements for NPN support to TS38.463 | ZTE Corporation |
| R3-200342 | TP for NPN support to TS38.463 | ZTE Corporation |
| R3-200722 | (TP for NPN BL CR for TS 38.463): Further support of NPN over E1 | Huawei, China Telecommunication |
| R3-200723 | CR to TS 38.460 on support of NPN | Huawei, China Telecommunication |
| R3-200904 | NPN – E1 Aspects | Ericsson |
| R3-200905 | [TP for NPN BL CR 38.463] Introduction of further NPN E1AP content | Ericsson |
| R3-200973 | NPN – E1 Aspects | Ericsson |
| R3-200974 | [TP for NPN BL CR 38.463] Introduction of further NPN E1AP content | Ericsson |
| R3-201174 | Summary of offline discussion for CB: # 80_Email080-NPN_E1 | Ericsson |
| R3-201314 | [TP for NPN BL CR 38.463] Introduction of further NPN E1AP content | Ericsson |
| R3-201337 | CR to TS 38.460 on support of NPN | Huawei, China Telecom |
| 16.2.8 | Dual Connectivity Aspects | |
| R3-200202 | (TP for NPN BL CR for 38.300) Dual Connectivity aspects of NPN | Nokia, Nokia Shanghai Bell |
| R3-200724 | Support of MR-DC for NPN | Huawei |
| R3-200906 | NPN – Dual Connectivity Aspects | Ericsson |
| R3-200975 | NPN – Dual Connectivity Aspects | Ericsson |
| R3-201175 | Summary of offline discussion for CB: # 81_Email081-NPN_DC | Nokia |
| 16.2.9 | RAN Sharing Aspects | |
| R3-200159 | Discussion on NPN RAN sharing | China Telecommunication |
| R3-200203 | (TP for NPN BL CR for 38.300) Correction of NPN RAN sharing | Nokia, Nokia Shanghai Bell |
| R3-200447 | Discussion on RAN sharing for NPNs | CATT |
| R3-200725 | (TP for NPN BL CR for TS 38.300): Support of RAN sharing with NPN | Huawei |
| R3-200907 | NPN – RAN Sharing Aspects | Ericsson |
| R3-200976 | NPN – RAN Sharing Aspects | Ericsson |
| R3-201176 | Summary of offline discussion for CB: # 82_Email082-NPN_RANsharing | CATT |
| R3-201251 | (TP for NPN BL CR for 38.300) Correction of NPN RAN sharing | Nokia, Nokia Shanghai Bell |
| R3-201319 | NPN – RAN Sharing Aspects | Ericsson |
| 16.2.10 | Others | |
| R3-200726 | Connection management between PLMN and SNPN | Huawei |
| 17.1 | General | |
| R3-200053 | Introduction of NR_IIOT support to TS 38.300 | CATT, Ericsson, Samsung, Huawei, ZTE, Nokia |
| R3-200054 | Introduction of NR_IIOT support to TS 38.415 | Nokia, Nokia Shanghai Bell |
| R3-200055 | Resource efficient PDCP duplication: enhancement 3 | Huawei, CMCC |
| R3-200056 | Introduction of NR_IIOT support to TS 38.413 | Nokia, Nokia Shanghai Bell, Huawei |
| R3-200057 | Introduction of NR_IIOT support to 38.423 | Ericsson |
| R3-200058 | Introduction of NR_IIOT support to 38.463 | ZTE |
| R3-200059 | Introduction of NR_IIOT support to TS 38.473 | Huawei |
| R3-201070 | (TP for NR_IIOT BL CR for TS 38.423) Corrections to BL CR | Nokia, Nokia Shanghai Bell |
| R3-201177 | Summary of offline discussion for CB: # 95_Email095-IIoT_BLs | Nokia |
| R3-201464 | NRIIOT Higher Layer Multi-Connectivity | CATT, Ericsson, Samsung, Huawei, ZTE, Nokia |
| R3-201465 | Introduction of NR_IIOT support to TS 38.413 | Nokia, Nokia Shanghai Bell, Huawei |
| R3-201466 | Introduction of NR_IIOT support to TS 38.423 | Ericsson |
| R3-201467 | Resource efficient PDCP duplication: enhancement 3 | Huawei, CMCC, Ericsson |
| R3-201468 | Introduction of NR_IIOT support to TS 38.463 | ZTE |
| R3-201469 | Introduction of NR_IIOT support to TS 38.473 | Huawei |
| 17.2.1 | PDCP Duplication for CA-only and for NR DC with CA | |
| R3-200256 | (TP for Introduction of NR_IIOT support to 38.423) Supporting duplication for more than 2 RLC entities | ZTE |
| R3-200257 | (TP for Introduction of NR_IIOT support to 38.473) Supporting duplication for more than 2 RLC entities | ZTE |
| R3-200258 | (TP for Introduction of NR_IIOT support to 38.463) Supporting duplication for more than 2 RLC entities | ZTE |
| R3-200908 | Up to Four RLC entities in the PDCP Duplication | Ericsson |
| R3-200977 | Up to Four RLC entities in the PDCP Duplication | Ericsson |
| R3-201045 | (TP for NR_IIOT BL CR for TS 38.423): PDCP duplication with more than 2 entities | Huawei |
| R3-201046 | (TP for NR_IIOT BL CR for TS 38.463): PDCP duplication with more than 2 entities | Huawei |
| R3-201047 | (TP for NR_IIOT BL CR for TS 38.473): PDCP duplication with more than 2 entities | Huawei |
| R3-201178 | Summary of offline discussion for CB: # 96_Email096-IIoT_PDCPdup_morethan2 | Ericsson |
| R3-201352 | Up to Four RLC entities in the PDCP Duplication | Ericsson |
| R3-201353 | (TP for Introduction of NR_IIOT support to 38.463) Supporting duplication for more than 2 RLC entities | ZTE |
| R3-201354 | (TP for NR_IIOT BL CR for TS 38.473): PDCP duplication with more than 2 entities | Huawei |
| R3-201403 | Up to Four RLC entities in the PDCP Duplication | Ericsson |
| 17.2.2 | Dynamic Control | |
| R3-200224 | On Coordination for PDCP Duplication with NR-DC/CA Combination | Nokia, Nokia Shanghai Bell |
| R3-200225 | (TPs for NR_IIoT BL CRs for TS 38.423 and for TS 38.425): Enabling coordination for duplication over more than 2 RLCs | Nokia, Nokia Shanghai Bell |
| R3-200259 | Consideration on PDCP UL duplication coordination for more than 2 RLC entities | ZTE |
| R3-200260 | TP for PDCP UL duplication coordination to TS38.425 | ZTE |
| R3-200279 | Network coordination for UL PDCP duplication | Qualcomm Incorporated |
| R3-200536 | Discussion on handling of UL PDCP Duplication status information | CATT |
| R3-200537 | (TP for [NR_IIOT] BL CR for TS 38.25)Discussion on handling of UL PDCP Duplication status information | CATT |
| R3-200598 | Dynamic control of PDCP duplication | CMCC |
| R3-200909 | Dynamic Control of PDCP Duplication | Ericsson |
| R3-200978 | Dynamic Control of PDCP Duplication | Ericsson |
| R3-201048 | (TP for NR_IIOT BL CR for TS 38.425): Assistance information for DL PDCP duplication with more than 2 entities | Huawei, CMCC |
| R3-201049 | (TP for NR_IIOT BL CR for TS 38.425): Dynamic control of UL duplication | Huawei |
| R3-201179 | Summary of offline discussion for CB: # 97_Email097-IIoT_PDCPdup_dyn_ctrl | CMCC |
| 17.2.3 | Enhancements for More Efficient DL PDCP Duplication | |
| R3-200261 | Further discussion on enhancement1 for more efficient PDCP duplication | ZTE |
| R3-200262 | TP for enhancement1 for more efficient PDCP duplication to TS38.425 | ZTE |
| R3-200782 | Even more simplified solution to make duplication actually more efficient | Nokia, Nokia Shanghai Bell |
| R3-200783 | (TP for NR_IIoT BL CR for TS 38.425): Increasing duplication efficiency by avoiding unnecessary duplication | Nokia, Nokia Shanghai Bell |
| R3-200910 | Further discussion on Enhancements for More Efficient DL PDCP Duplication | Ericsson |
| R3-200911 | Resolving FFS for Enhancement 3 | Ericsson |
| R3-200979 | Further discussion on Enhancements for More Efficient DL PDCP Duplication | Ericsson |
| R3-200980 | Resolving FFS for Enhancement 3 | Ericsson |
| R3-201050 | Resource efficient PDCP duplication | Huawei |
| R3-201051 | (TP for NR_IIOT BL CR for TS 38.425): Resource efficient PDCP duplication: enhancement 3 | Huawei, CMCC |
| R3-201180 | Summary of offline discussion for CB: # 98_Email098-IIoT_PDCPdup_enh | Huawei |
| 17.2.4.1 | Common (Stage 2) | |
| R3-200988 | TP for resolving FFS in stage 2 | Ericsson |
| R3-201052 | (TP for NR_IIOT BL CR for TS 38.300): Higher layer duplication | Huawei |
| R3-201053 | Higher layer duplication for TS 37.340 | Huawei |
| R3-201181 | Summary of offline discussion for CB: # 99_Email099-IIoT_HLmulticonn_st2 | Huawei |
| 17.2.4.2 | Solution #1 | |
| R3-200204 | (TP for BL CR NR IIoT for 38.423) Redundant PDU sessions over Xn for solution 1 | Nokia, Nokia Shanghai Bell |
| R3-200248 | (TP for Introduction of NR_IIOT support to TS38.413): Redundant PDU session establishment | ZTE |
| R3-200249 | (TP for Introduction of NR_IIOT support to TS38.423): Redundant PDU session establishment | ZTE |
| R3-200250 | (TP for Introduction of NR_IIOT support to TS38.463): Redundant PDU session establishment | ZTE |
| R3-200251 | (TP for Introduction of NR_IIOT support to TS38.423): Disjoint UP path quantity at SN transfer | ZTE, CATT |
| R3-200252 | (TP for Introduction of NR_IIOT support to TS38.463): Disjoint UP path quantity at SN transfer | ZTE, CATT |
| R3-200538 | Discussion on Higher Layer Multi-Connectivity Solution#1 | CATT |
| R3-200539 | (TP for [NR_IIOT] BL CR for TS 38.413)NRIIOT Higher Layer Multi-Connectivity Solution#1 | CATT |
| R3-200540 | (TP for [NR_IIOT] BL CR for TS 38.423)NRIIOT Higher Layer Multi-Connectivity Solution#1 | CATT |
| R3-200541 | (TP for [NR_IIOT] BL CR for TS 38.463)NRIIOT Higher Layer Multi-Connectivity Solution#1 | CATT |
| R3-200581 | (TP for NR_IIOT BL CR for TS 38.413): Redundant PDU session setup | Samsung |
| R3-200582 | (TP for NR_IIOT BL CR for TS 38.423): Redundant PDU session setup | Samsung |
| R3-200583 | (TP for NR_IIOT BL CR for TS 38.413): The indications of the Secondary RAN to SMF | Samsung |
| R3-200786 | Discussion on remaining issues for Solution #1 | LG Electronics |
| R3-200787 | Introduction of Redundant Transmission Information for Solution #1 (TS 38.413) | LG Electronics |
| R3-200788 | Introduction of Redundant Transmission Information for Solution #1 (TS 38.423) | LG Electronics |
| R3-200789 | Introduction of Redundant Transmission Information for Solution #1 (TS 38.463) | LG Electronics |
| R3-200912 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson |
| R3-200913 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson |
| R3-200914 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson |
| R3-200915 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson |
| R3-200981 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson |
| R3-200982 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson |
| R3-200983 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson |
| R3-200984 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson |
| R3-201054 | (TP for NR_IIOT BL CR for TS 38.413): Higher layer duplication for solution 1 | Huawei |
| R3-201055 | (TP for NR_IIOT BL CR for TS 38.423): Higher layer duplication for solution 1 | Huawei |
| R3-201056 | (TP for NR_IIOT BL CR for TS 38.463): Higher layer duplication for solution 1 | Huawei |
| R3-201182 | Summary of offline discussion for CB: # 100_Email100-IIoT_HLmulticonn_sol1 | CATT |
| R3-201264 | (TP for [NR_IIOT] BL CR for TS 38.413)NRIIOT Higher Layer Multi-Connectivity Solution#1 | CATT |
| R3-201265 | (TP for Introduction of NR_IIOT support to TS38.423): Redundant PDU session establishment | ZTE |
| 17.2.4.3 | Solution #4 | |
| R3-200205 | (TP for BL CR NR IIoT for 38.413) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| R3-200206 | (TP for BL CR NR IIoT for 38.423) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| R3-200207 | (TP for BL CR NR IIoT for 38.463) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| R3-200208 | (TP for BL CR NR IIoT for 38.300) Correction of redundant forwarding tunnels | Nokia, Nokia Shanghai Bell |
| R3-200209 | LS on data forwarding and redundant transmission over N3 | Nokia, Nokia Shanghai Bell |
| R3-200253 | (TP for Introduction of NR_IIOT support to TS38.413): Solution4 modification | ZTE |
| R3-200254 | (TP for Introduction of NR_IIOT support to TS38.423): Solution4 modification | ZTE |
| R3-200255 | (TP for Introduction of NR_IIOT support to TS38.463): Solution4 modification | ZTE |
| R3-200542 | Discussion on Higher Layer Multi-Connectivity Solution#4 | CATT |
| R3-200543 | (TP for [NR_IIOT] BL CR for TS 38.413)NRIIOT Higher Layer Multi-Connectivity Solution#4 | CATT |
| R3-200544 | (TP for [NR_IIOT] BL CR for TS 38.423)NRIIOT Higher Layer Multi-Connectivity Solution#4 | CATT |
| R3-200545 | (TP for [NR_IIOT] BL CR for TS 38.463)NRIIOT Higher Layer Multi-Connectivity Solution#4 | CATT |
| R3-200916 | Solution #4 of Key Issue 1: Resolving FFS | Ericsson |
| R3-200917 | Solution #4 of Key Issue 1: Resolving FFS | Ericsson |
| R3-200918 | Solution #4 of Key Issue 1: Resolving FFS | Ericsson |
| R3-200919 | TP for resolving FFS in stage 2 | Ericsson |
| R3-200985 | Solution #4 of Key Issue 1: Resolving FFS | Ericsson |
| R3-200986 | Solution #4 of Key Issue 1: Resolving FFS | Ericsson |
| R3-200987 | Solution #4 of Key Issue 1: Resolving FFS | Ericsson |
| R3-201057 | (TP for NR_IIOT BL CR for TS 38.413): Higher layer duplication for solution 4 | Huawei |
| R3-201058 | (TP for NR_IIOT BL CR for TS 38.423): Higher layer duplication for solution 4 | Huawei |
| R3-201059 | (TP for NR_IIOT BL CR for TS 38.463): Higher layer duplication for solution 4 | Huawei |
| R3-201183 | Summary of offline discussion for CB: # 101_Email101-IIoT_HLmulticonn_sol4 | Ericsson |
| R3-201344 | Solution #4 of Key Issue 1: Resolving FFS | Ericsson |
| R3-201345 | (TP for Introduction of NR_IIOT support to TS38.463): Solution4 modification | ZTE, Ericsson |
| R3-201381 | (TP for BL CR NR IIoT for 38.413) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| 17.3.2 | TSC Assistance Information | |
| R3-200280 | (TP for NR_IIOT BL CR for TS 38.413) Adding separate uplink / downlink CN PDB | Qualcomm Incorporated |
| R3-201060 | (TP for NR_IIOT BL CR for TS 38.413):TSC Assistance Information | Huawei |
| R3-201061 | (TP for NR_IIOT BL CR for TS 38.423):TSC Assistance Information | Huawei |
| R3-201062 | (TP for NR_IIOT BL CR for TS 38.473):TSC Assistance Information | Huawei |
| R3-201184 | Summary of offline discussion for CB: # 102_Email102-IIoT_TSC_assist_info | Huawei |
| R3-201302 | (TP for NR_IIOT BL CR for TS 38.463):TSC Assistance Information | ZTE |
| 17.3.3 | Time Reference Information | |
| R3-200243 | (TP for NR_IIOT BL CR for TS 38.473): On SIB9 Broadcast | Nokia, Nokia Shanghai Bell |
| R3-200263 | (TP to BL CR#0477 Introduction of NR_IIOT support to TS 38.473) Update the value range of parameters | ZTE |
| R3-200920 | Resolving FFS related to Time Reference Information | Ericsson |
| R3-200989 | Resolving FFS related to Time Reference Information | Ericsson |
| R3-201063 | (TP for NR_IIOT BL CR for TS 38.473): Reference timing information | Huawei |
| R3-201185 | Summary of offline discussion for CB: # 103_Email103-IIoT_time_ref_info | Ericsson |
| R3-201343 | Resolving FFS related to Time Reference Information | Ericsson |
| 17.4 | Others | |
| R3-201064 | (TP for NR_IIoT BL CR for TS 38.300) : Introduction of CN PDB | Huawei |
| 18.1 | General | |
| R3-200739 | Work plan for RACS-RAN work item | CATT, MediaTek Inc. |
| R3-200740 | Work plan for RACS-RAN work item | CATT, MediaTek Inc. |
| R3-200741 | Work plan for RACS-RAN work item | CATT, MediaTek Inc. |
| R3-200742 | Work plan for RACS-RAN work item | CATT, MediaTek Inc. |
| R3-200743 | Work plan for RACS-RAN work item | CATT, MediaTek Inc. |
| 18.2 | Optimizing UE Radio Capability Signaling using UE Capability Identity | |
| R3-201186 | Summary of offline discussion for CB: # 2_Email002-RACS | Samsung |
| 18.2.1 | Common | |
| R3-200287 | RACS impacts in RAN3 specifications | Qualcomm Incorporated |
| R3-200307 | Discussion on support of RACS | CATT |
| R3-200348 | RACS, UE Radio Access Capability related ID and information | NEC |
| R3-200394 | Signalling UE capability Identity | Huawei |
| R3-200706 | RACS Support – S1/NG and X2/Xn | Samsung Electronics |
| R3-200707 | S1AP support for Radio Capability Signaling Optimization | Samsung Electronics |
| R3-200708 | X2AP support for Radio Capability Signaling Optimization | Samsung Electronics |
| R3-200727 | NGAP support for Radio Capability Signaling Optimization | Samsung Electronics |
| R3-200732 | XnAP support for Radio Capability Signaling Optimization | Samsung Electronics |
| R3-200820 | Introducing Radio Capability Optimisation (RACS) | Ericsson |
| R3-200821 | Introducing Radio Capability Optimisation (RACS) | Ericsson |
| R3-200823 | RACS work in RAN3 | Ericsson |
| R3-200824 | Introducing Radio Capability Optimisation (RACS) | Ericsson |
| R3-200825 | Introducing Radio Capability Optimisation (RACS) | Ericsson |
| R3-201299 | X2AP support for Radio Capability Signaling Optimization | Samsung, CATT, Ericsson, Huawei, Qualcomm |
| R3-201300 | Introducing Radio Capability Optimisation (RACS) | Ericsson |
| R3-201426 | Introducing Radio Capability Optimisation (RACS) | Ericsson, Qualcomm, CATT, Samsung, Huawei |
| 18.2.2 | 5GC Specific Aspects | |
| R3-200288 | Introduction of RACS support | Qualcomm Incorporated |
| R3-200308 | supporting of RACS in NG | CATT |
| R3-200309 | supporting of RACS in Xn | CATT |
| R3-200395 | Signalling UE capability Identity | Huawei |
| R3-200396 | Signalling UE capability Identity | Huawei |
| R3-201301 | Supporting of RACS in XnAP | CATT, Samsung, Huawei, Ericsson, Qualcomm |
| 18.2.3 | EPS Specific Aspects | |
| R3-200310 | supporting of RACS in S1 | CATT |
| R3-200311 | supporting of RACS in X2 | CATT |
| R3-200397 | Signalling UE capability Identity | Huawei |
| R3-200398 | Signalling UE capability Identity | Huawei |
| R3-201289 | Signalling UE capability Identity | Huawei, Samsung Electronics, CATT, Ericsson, Qualcomm |
| 19.1 | General | |
| R3-200060 | Transmission Measurement Function in NG-RAN | Ericsson |
| R3-200061 | Introduction of positioning support over F1AP | Qualcomm Incorporated |
| R3-200062 | Positioning support over F1AP | Huawei |
| R3-200063 | Introduction of NR Positioning | Ericsson |
| R3-200777 | Introduction of NR Positioning in NRPPa | Ericsson |
| R3-200784 | Introduction of NR Positioning | Ericsson |
| R3-201016 | [TP to BL CR for TS 38.305] correction on NG-RAN architecture | Ericsson, Intel |
| R3-201187 | Summary of offline discussion for CB: # 56_Email056-Pos_BLs | Intel |
| R3-201373 | [TP to BL CR for TS 38.305] correction on NG-RAN architecture | Ericsson, Intel |
| R3-201392 | Summary of offline discussion for CB: # 56_Email056-Pos_BLs | Intel |
| R3-201470 | Running CR for the introduction of NR positioning | Ericsson |
| R3-201471 | Introduction of NR Positioning in NRPPa | Ericsson, Intel |
| R3-201472 | Positioning support over F1AP | Huawei |
| 19.2 | NRPPa Extensions for RAT-Dependent Positioning | |
| R3-200426 | (TP for NR_POS BL CR for TS 38.455) NRPPa changes to support Exchange of TRP Information and Measurements by specific TRPs | Qualcomm Incorporated |
| R3-200457 | Discussion on SRS related UL positioning procedure | Huawei |
| R3-200458 | Multiple discussions on NRPPa (FFS & TRP & TP) | Huawei |
| R3-200479 | (TP for NR_POS BL CR for TS 38.455) Additional details for NRPPa Measurement procedures | Nokia, Nokia Shanghai Bell |
| R3-200480 | TRP configuration information exchange | Nokia, Nokia Shanghai Bell |
| R3-200778 | Positioning measurements support in NRPPa | Intel Corporation |
| R3-200779 | (TP for BL CR 38.455) Positioning measurements | Intel Corporation |
| R3-201017 | Exchange of DL PRS configuration over Xn | Ericsson |
| R3-201018 | Introduction of DL PRS configuration exchange over Xn | Ericsson |
| R3-201188 | Summary of offline discussion for CB: # 57_Email057-Pos_NRPPa_ext | Nokia |
| R3-201189 | Summary of offline discussion for CB: # 58_Email058-Pos_PRSexchange_Xn | Ericsson |
| R3-201290 | (TP for NR_POS BL CR for 38.455) NRPPa extensions for RAT-dependent positioning | Nokia, Nokia Shanghai Bell |
| 19.3 | Transmission Measurement Function | |
| R3-201019 | Reporting of UL AoA beam info to LMF | Ericsson |
| 19.4 | Broadcast Assistance Data Delivery | |
| R3-200424 | (TP for NR_POS BL CR for TS 38.455) NRPPa open issues for Broadcast Assistance Data Delivery | Qualcomm Incorporated |
| R3-200425 | (TP for NR_POS BL CR for TS 38.473) F1AP issues for Broadcast Assistance Data Delivery | Qualcomm Incorporated |
| R3-200459 | (TP for BL CR for TS 38.455) NR Assistance Data Delivery | Huawei |
| R3-200460 | (TP for BL CR for TS 38.473): F1 support for NR positioning | Huawei |
| R3-200546 | Introduce Positioning SI Area ID | CATT |
| R3-200547 | (TP for [NR_POS-Core] BL CR for TS 38.455) Introduce Positioning SI Area ID | CATT |
| R3-201020 | Discussion on remaining FFS of delivery of Positioning Assistance Data over F1AP | Ericsson |
| R3-201021 | [TP to BL CR for TS 38.470] Positioning support over F1AP | Ericsson |
| R3-201190 | Summary of offline discussion for CB: # 59_Email059-Pos_Broadcast_Assist | Huawei |
| 19.5 | Positioning Support in split gNB Architecture | |
| R3-200461 | (TP for BL CR for TS 38.470): F1 support for NR positioning | Huawei |
| R3-200462 | F1 support for positioning | Huawei |
| R3-200776 | (TP for NR_POS BL CR for TS 38.473) F1AP changes to support Exchange of TRP Information | Qualcomm Incorporated |
| R3-200780 | Positioning measurements support in F1-AP | Intel Corporation |
| R3-200781 | (TP for BL CR 38.473) Positioning measurements | Intel Corporation |
| R3-201191 | Summary of offline discussion for CB: # 60_Email060-Pos_split_gNB_arch | Qualcomm |
| 20.1 | General | |
| R3-200064 | Support of NR V2X over F1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-200065 | Support of NR V2X over S1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-200066 | Support of NR V2X over X2 | CATT, Huawei, Ericsson, LG Electronics |
| R3-200067 | Support of NR V2X over NG | LG Electronics, Ericsson, Huawei, CATT |
| R3-200068 | Support of NR V2X over Xn | Ericsson,LG Electronics, CATT, Huawei |
| R3-201192 | Summary of offline discussion for CB: # 52_Email052-V2X_BLs | LG |
| R3-201439 | Support of NR V2X over S1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-201440 | Support of NR V2X over X2 | CATT, Huawei, Ericsson, LG Electronics |
| R3-201441 | Support of NR V2X over NG | LG Electronics, Ericsson, Huawei, CATT |
| R3-201442 | Support of NR V2X over Xn | Ericsson, LG Electronics, CATT, Huawei |
| R3-201443 | Support of NR V2X over F1 | Huawei, LG Electronics, Ericsson, CATT |
| 20.2.2 | V2X Support over F1 | |
| R3-200237 | Consideration on remaining Issues on F1 | LG Electronics |
| R3-200474 | Discussion on leftover issues on F1 interface | ZTE, Sanechips |
| R3-200475 | Discussion on Tx profile | ZTE, Sanechips |
| R3-200653 | (TP for BLCR 38.473) on remaining Issues on F1 | LG Electronics |
| R3-200695 | (TP for V2X BL CR for TS 38.473) System information for sidelink over F1 | Huawei |
| R3-200696 | (TP for V2X BL CR for TS 38.473) Sidelink resource request over F1 | Huawei |
| R3-201022 | Discussion on remaining aspects of support of NR V2X over F1 | Ericsson |
| R3-201023 | Support of NR V2X SIB in gNB-DU | Ericsson |
| R3-201193 | Summary of offline discussion for CB: # 53_Email053-V2X_F1 | ZTE |
| R3-201394 | Support of NR V2X SIB in gNB-DU | Ericsson |
| 20.2.3 | Resource Coordination between NG-RAN Nodes for V2X Sidelink | |
| R3-200483 | Further consideration on resource coordination between NG-RAN nodes for V2X sidelink | LG Electronics |
| R3-200697 | (TP for V2X BL CR for TS 36.423) Remove FFS for V2X configuration exchange | Huawei |
| R3-200698 | (TP for V2X BL CR for TS 38.423 & 38.473) Remove FFS for V2X configuration exchange | Huawei |
| R3-201024 | Discussion on support of V2X resource coordination between NG-RAN nodes | Ericsson |
| R3-201025 | TP to XnAP BL CR: support of V2X resource coordination over Xn | Ericsson |
| R3-201194 | Summary of offline discussion for CB: # 54_Email054-V2X_resource_coord | Ericsson |
| 20.2.4 | Support for QoS | |
| R3-200226 | Support for alternative QoS profiles | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-200227 | (TP for BL CR V2X for 38.413) Support for alternative QoS profiles over NG | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-200228 | Reply LS on Enhancements to QoS Handling for V2X communication over Uu reference point | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-200302 | Support of PC5 QoS Parameters for NR V2X | CATT, LG Electronics, Samsung, Ericsson, Huawei |
| R3-200303 | (TP for NR BL CR for TS 38.413) Support of PC5 QoS Parameters for NR V2X | CATT, LG Electronics, Samsung, Ericsson, Huawei |
| R3-200304 | (TP for NR BL CR for TS 38.423) Support of PC5 QoS Parameters for NR V2X | CATT, LG Electronics, Samsung, Ericsson, Huawei |
| R3-200305 | (TP for NR BL CR for TS 36.413) Support of PC5 QoS Parameters for NR V2X | CATT, LG Electronics, Samsung, Ericsson, Huawei |
| R3-200306 | (TP for NR BL CR for TS 36.423) Support of PC5 QoS Parameters for NR V2X | CATT, LG Electronics, Samsung, Ericsson, Huawei |
| R3-200476 | (TP for 5G_V2X_NRSL BL CR for TS 38.473): SLRB configuration | ZTE, Sanechips |
| R3-200699 | Discussion on Alternative QoS Profiles | Huawei, Orange |
| R3-200700 | Support of Alternative QoS Profiles | Huawei, Vodafone, Orange |
| R3-200701 | Support of Alternative QoS Profiles | Huawei, Orange |
| R3-200702 | Support of Alternative QoS Profiles | Huawei, Orange |
| R3-201026 | TP to XnAP BL CR: support of Alternative QoS profiles over Xn | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-201027 | TP to F1AP BL CR: support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-201029 | Support of alternative QoS profiles for V2X and handover into congested cells | VODAFONE Group Plc |
| R3-201031 | Full support of alternative QoS profiles | VODAFONE Group Plc |
| R3-201033 | Support of alternative QoS profiles | VODAFONE Group Plc |
| R3-201195 | Summary of offline discussion for CB: # 55_Email055-V2X_AltQoS | Nokia |
| R3-201229 | Summary of offline discussion on V2XPC5 QoS Parameters | CATT |
| R3-201250 | (TP for BL CR V2X for 38.413) Support for alternative QoS profiles over NG | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-201284 | Reply LS on Enhancements to QoS Handling for V2X communication over Uu reference point | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-201291 | TP to XnAP BL CR: support of Alternative QoS profiles over Xn | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-201292 | TP to F1AP BL CR: support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-201395 | (TP for 5G_V2X_NRSL BL CR for TS 38.473): SLRB configuration | ZTE, Sanechips |
| 21.1 | General | |
| R3-200069 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom |
| R3-200070 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom |
| R3-200389 | Updated work plan for WWC | Huawei |
| R3-201196 | Summary of offline discussion for CB: # 37_Email037-WWC_general | Huawei |
| R3-201444 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom |
| R3-201445 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom |
| 21.2 | NG Support for WWC | |
| R3-201197 | Summary of offline discussion for CB: # 38_Email038-WWC_TPs | Huawei |
| 21.2.2 | Support for Interfacing Trusted non-3GPP Access Networks to the 5GC | |
| R3-200390 | (TP for WWC BL CR for TS 29.413): Support for interfacing Trusted non-3GPP Access Networks to the 5GC | Huawei, Telecom Italia, BT, Broadcom |
| R3-200391 | (TP for WWC BL CR for TS 38.413): Support for interfacing Trusted non-3GPP Access Networks to the 5GC | Huawei, Telecom Italia, BT, Broadcom, CMCC |
| R3-201253 | (TP for WWC BL CR for TS 29.413): Support for interfacing Trusted non-3GPP Access Networks to the 5GC | Huawei, Telecom Italia, BT, Broadcom |
| R3-201254 | (TP for WWC BL CR for TS 38.413): Support for interfacing Trusted non-3GPP Access Networks to the 5GC | Huawei, Telecom Italia, BT, Broadcom, CMCC |
| 21.2.3 | Support for Interfacing Wireline 5G Access Networks to the 5GC | |
| R3-200392 | (TP for WWC BL CR for TS 29.413): Support for interfacing Wireline 5G Access Networks to the 5GC | Huawei, Telecom Italia, BT, Broadcom |
| R3-200393 | (TP for WWC BL CR for TS 38.413): Support for interfacing Wireline 5G Access Networks to the 5GC | Huawei, Telecom Italia, BT, Broadcom |
| R3-201255 | (TP for WWC BL CR for TS 29.413): Support for interfacing Wireline 5G Access Networks to the 5GC | Huawei, Telecom Italia, BT, Broadcom |
| R3-201256 | (TP for WWC BL CR for TS 38.413): Support for interfacing Wireline 5G Access Networks to the 5GC | Huawei, Telecom Italia, BT, Broadcom |
| 30.1 | NR-U | |
| R3-200281 | Further discussion on NR-U impacts | Qualcomm Incorporated, Charter Communications, Nokia, Nokia Shanghai Bell |
| R3-200282 | Introduction of NR-U | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-200283 | Introduction of NR-U | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-200284 | Introduction of NR-U | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-200285 | Introduction of NR-U | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-200665 | Signalling support of NR-U | Huawei |
| R3-200666 | Signalling support of NR-U | Huawei |
| R3-200667 | Signalling support of NR-U | Huawei |
| R3-200668 | Signalling support of NR-U | Huawei |
| R3-200669 | Signalling support of NR-U | Huawei |
| R3-201198 | Summary of offline discussion for CB: # 11_Email011-NR-U | Qualcomm |
| R3-201293 | Introduction of NR-U | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-201294 | Introduction of NR-U | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-201295 | Introduction of NR-U | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-201296 | Introduction of NR-U | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| 30.2 | Support for NavIC Navigation Satellite System for LTE | |
| R3-200135 | Enabling NavIC assistance data support | Reliance Jio, CEWiT, Huawei, ISRO, MediaTek Inc., Qualcomm Incorporated, Saankhya Labs Private Limited, Tejas Networks Ltd. |
| R3-201283 | Enabling NavIC assistance data support | Reliance Jio, CEWiT, Huawei, ISRO, MediaTek Inc., Qualcomm Incorporated, Saankhya Labs Private Limited, Tejas Networks Ltd. |
| R3-201438 | CR of TS 36.455 for introducing NavIC in LTE - core part | Reliance Jio, CEWiT, Ericsson, Huawei, ISRO, MediaTek Inc., Qualcomm Incorporated, Saankhya Labs Private Limited, Tejas Networks Ltd. |
| 30.3 | SRVCC WI | |
| R3-200071 | Support SRVCC from 5G to 3G | Ericsson |
| R3-200072 | Introduction of 5G-SRVCC | Nokia, Nokia Shanghai Bell |
| R3-200073 | Support of SRVCC from 5G to 3G | Huawei, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated |
| R3-200552 | Introduction of 5Gto3GSRVCC Dedicated Failure Cause Value | ZTE |
| 31.2.2 | Reporting NR Cells as Inter-RAT Measurements in LPPa | |
| R3-201028 | Inter-RAT Measurement of NR Cells for E-CID | Ericsson, NTT DOCOMO, Nokia, Nokia Shanghai Bell, Huawei |
| R3-201199 | Summary of offline discussion for CB: # 12_Email012-InterRAT_measuements_E-CID_LPPa | Ericsson |
| R3-201486 | Inter-RAT Measurement of NR Cells for E-CID | Ericsson, NTT DOCOMO, Nokia, Nokia Shanghai Bell, Huawei |
| 31.2.3 | Broadcast of TBS, Barometric Pressure Assistance Data | |
| R3-200235 | Addition of broadcast of barometric pressure assistance data | Polaris Wireless, FirstNet, Intel, AT&T, NextNav |
| R3-200278 | Broadcast of TBS assistance data | NextNav, AT&T, FirstNet, Polaris Wireless |
| R3-201200 | Summary of offline discussion for CB: # 13_Email013-TBSassistance_LPPa | AT&T |
| R3-201383 | Addition of broadcast of barometric pressure and TBS assistance data | Polaris Wireless, FirstNet, Intel, AT&T, NextNav |
| R3-201428 | Addition of broadcast of barometric pressure and TBS assistance data | AT&T, FirstNet, Intel, NetNav, Polaris Wireless |
| 31.3.1 | Multiple SCTP Associations in X2 | |
| R3-200482 | CR to 36.422 for Supporting mutiple SCTP assoication in EN-DC | China Telecom Corporation Ltd. |
| R3-200556 | The support for Multiple-SCTP over EN-DC X2 | Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, TELECOM ITALIA, Intel Corporation, Orange, China Mobile |
| R3-200557 | Support for Multiple SCTP | Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, TELECOM ITALIA, Intel Corporation, Orange, China Mobile |
| R3-200584 | CR to 36.422 for Supporting mutiple SCTP assoication in EN-DC | China Telecom, Nokia, Nokia Shanghai Bell, China Unicom, TELECOM ITALIA, Intel Corporation, Orange, China Mobile |
| R3-201201 | Summary of offline discussion for CB: # 14_Email014-multiSCTPAssoc_X2 | Nokia |
| R3-201490 | Support for Multiple SCTP | Nokia, Nokia Shanghai Bell, China Telecom, China Unicom, TELECOM ITALIA, Intel Corporation, Orange, China Mobile |
| R3-201491 | CR to 36.422 for Supporting mutiple SCTP assoication in EN-DC | China Telecom, Nokia, Nokia Shanghai Bell, China Unicom, TELECOM ITALIA, Intel Corporation, Orange, China Mobile |
| 31.3.2 | Clarification on Initial UL RRC Message Transfer | |
| R3-200648 | Further discussions on including MSG4 during Initial UL RRC Message Transfer procedure | Huawei |
| R3-200797 | Clarification on Initial UL RRC Message Transfer procedure | Ericsson |
| R3-200798 | RRC Container IE in Initial UL RRC Message Transfer procedure | Ericsson |
| R3-200921 | Clarification on Initial UL RRC Message Transfer procedure | Ericsson |
| R3-200990 | Discussion on clarification on Initial UL RRC Message Transfer procedure | Ericsson |
| R3-201202 | Summary of offline discussion for CB: # 15_Email015-Initial_UL_RRC_Mess_Trsf | Ericsson |
| 31.3.3 | Direct Data Forwarding Between NG-RAN and E-UTRAN | |
| R3-200229 | Inter-system direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, Samsung, CATT, China Telecom |
| R3-200579 | Inter-system direct forwarding with shared SgNB/gNB | Samsung, Nokia, Nokia Shanghai Bell, CATT, China Telecom |
| R3-200580 | Inter-system direct forwarding with shared SgNB/gNB | Samsung, Nokia, Nokia Shanghai Bell, CATT, China Telecom |
| R3-200670 | Inter-system HO from EN-DC to SA with shared SgNB/gNB | Huawei |
| R3-200923 | On direct data forwarding with shared (S)en-gNB/gNB at inter-system handover from EPS to 5GS | Ericsson |
| R3-200991 | Enabling node-internal direct data forwarding in case of shared en-gNB/gNB for HO from EPS to 5GS | Ericsson |
| R3-200992 | On direct data forwarding with shared (S)en-gNB/gNB at inter-system handover from EPS to 5GS | Ericsson |
| R3-201203 | Summary of offline discussion for CB: # 16_Email016-DirectDataFwding | Huawei |
| R3-201227 | Inter-system direct forwarding with shared SgNB/gNB | Samsung, Nokia, Nokia Shanghai Bell, CATT, China Telecom |
| R3-201228 | Inter-system direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, Samsung, CATT, China Telecom |
| 31.3.4 | Ethernet Type Bearer Signaling in NG-RAN | |
| R3-200167 | Consideration on Ethernet Header Compression | Huawei |
| R3-200168 | Support of Ethernet Header Compression | Huawei, Samsung, CMCC |
| R3-200169 | Support of Ethernet Header Compression | Huawei |
| R3-200327 | Support of Ethernet Type Bearer | Huawei, Vodafone, Nokia |
| R3-200329 | Support of Ethernet Type Bearer | Huawei, Vodafone, Nokia |
| R3-200553 | TS38.463 Transfer of Bearer Type IE from CU-CP to CU-UP in EN-DC | ZTE |
| R3-201204 | Summary of offline discussion for CB: # 17_Email017-EthernetTypeBearer | Huawei |
| 31.3.5 | Node Name Type | |
| R3-200799 | Corrections to node name type | Ericsson |
| R3-200806 | Corrections to node name type | Ericsson |
| R3-200807 | Corrections to node name type | Ericsson |
| R3-200924 | Correction to node name format | Ericsson, Verizon, Samsung |
| R3-200993 | Correction to node name format | Ericsson, Verizon, Samsung |
| R3-201205 | Summary of offline discussion for CB: # 19bis_Email018-Node_name | Ericsson |
| 31.3.6 | Usage of Requested Fast MCG Recovery via SRB3 IE | |
| R3-200222 | Completion of the solution for fast link recovery for DC | Nokia, Nokia Shanghai Bell |
| R3-200223 | Completion of the solution for fast link recovery for DC | Nokia, Nokia Shanghai Bell |
| R3-200349 | Usage of Requested Fast MCG Recovery via SRB3 | NEC |
| R3-200350 | Correction of the Usage of Requested Fast MCG Recovery via SRB3 | NEC |
| R3-200351 | Correction of the Usage of Requested Fast MCG Recovery via SRB3 | NEC |
| R3-200554 | TS37.340 Stage2 Refined Descriptions of SCG Suspend&Resume Operation | ZTE |
| R3-200558 | TS36.423 Corrections of SCG Suspend&Release Behaviors with EN-DC in Rel-16 | ZTE |
| R3-200692 | Cleanup for Fast MCG link Recovery with SRB3 | Huawei |
| R3-200693 | Cleanup for Fast MCG link Recovery with SRB3 | Huawei |
| R3-200994 | Fast MCG link Recovery with SRB3 CR 38.423 | Ericsson |
| R3-200995 | Fast MCG link recovery via SRB3 CR 36.423 | Ericsson |
| R3-201206 | Summary of offline discussion for CB: # 19_Email019-FastMCGrecoverySRB3 | Huawei |
| R3-201350 | Cleanup for Fast MCG link Recovery with SRB3 | Huawei, Nokia, Nokia Shanghai Bell |
| R3-201351 | Cleanup for Fast MCG link Recovery with SRB3 | Huawei, Nokia, Nokia Shanghai Bell |
| R3-201398 | Summary of offline discussion for CB: # 19_Email019-FastMCGrecoverySRB3 | Huawei |
| 31.3.7.1 | Other Rel-16 Corrections | |
| R3-200240 | Discussion on Shared Transport | Nokia, Nokia Shanghai Bell |
| R3-200241 | Shared Transport between MN and SN in disaggregated architecture with F1 | Nokia, Nokia Shanghai Bell |
| R3-200242 | Shared Transport between MN and SN in disaggregated architecture with E1 | Nokia, Nokia Shanghai Bell |
| R3-200244 | GTP-U Error cause for F1 | Nokia, Nokia Shanghai Bell |
| R3-200245 | GTP-U Error cause for E1 | Nokia, Nokia Shanghai Bell |
| R3-200326 | Discussion on One PDU session with Multiple CU-UPs | ZTE Corporation |
| R3-200328 | Support one PDU session with multiple CU-UPs for TS38.401 | ZTE Corporation |
| R3-200330 | Support one PDU session with multiple CU-UPs for TS38.413 | ZTE Corporation |
| R3-200332 | Trace activation in the case of intra-CU inter-DU mobility | ZTE Corporation, China Unicom, China Telecom |
| R3-200377 | Correction of slice related cause values | Huawei |
| R3-200378 | Correction of slice related cause values | Huawei |
| R3-200379 | Corrections to CLI | Huawei |
| R3-200559 | TS38.300 Introduction of CSI-RS Based Measurement and Mobility for HO | ZTE |
| R3-200560 | TS38.300 Introduction of CSI-RS Based Measurement and Mobility for HO | ZTE |
| R3-200671 | Correction of last PDU session release | Huawei |
| R3-200683 | gNB-CU resiliency | NTT DOCOMO INC. |
| R3-200691 | Potential issue during modification procedure | Huawei, Vodafone, China Telecom, China Unicom |
| R3-200694 | Correction on resource coordination over F1 | Huawei |
| R3-200704 | CR for clarification on gNB-CU resiliency | NTT DOCOMO INC. |
| R3-200808 | gNB-CU-UP ID | Ericsson |
| R3-200927 | On the challenges of TNL address discovery with the flexible NG-RAN Node ID length | Ericsson, Verizon |
| R3-200928 | Draft LS on broadcasting gNB ID length in system information block | Ericsson, Verizon |
| R3-200996 | On the challenges of TNL address discovery with the flexible NG-RAN Node ID length | Ericsson, Verizon |
| R3-200997 | Draft LS on broadcasting gNB ID length in system information block | Ericsson, Verizon |
| R3-201035 | RAN UE ID for X2 | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-201036 | RAN UE ID for Xn | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-201037 | RAN UE ID for NG | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-201038 | Completion of RAN UE ID | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-201039 | gNB-CU-UP Graceful shutdown | Ericsson |
| R3-201040 | gNB-CU-UP graceful shutdown notification | Ericsson |
| R3-201071 | Signalling of Neighbour CSI-RS relation structure between NG-RAN nodes | Ericsson |
| R3-201086 | On Partial Failure | Nokia, Nokia Shanghai Bell |
| R3-201091 | Introduction of transaction ID during modification procedure | Huawei, China Telecom, China Unicom |
| R3-201092 | Introduction of transaction ID during modification procedure | Huawei, China Telecom, China Unicom |
| R3-201093 | Introduction of transaction ID during modification procedure | Huawei, China Telecom, China Unicom |
| R3-201257 | Corrections to CLI | Huawei |
| R3-201489 | Corrections to CLI | Huawei |
| 31.3.7.2 | Other TEI16 | |
| R3-200929 | Addition of Local NG-RAN Node Identifier. | Ericsson |
| R3-200998 | Addition of Local NG-RAN Node Identifier. | Ericsson |
| R3-200999 | Addition of Local NG-RAN Node Identifier to resolve NG-RAN ID from I-RNTI. | Ericsson |
| 31.4 | Rapporteur Corrections for Rel-16 | |
| R3-200153 | Rapporteur's Update for 38.472 | InterDigital |
| R3-200230 | Rapporteur Correction of TS 38.410 | Nokia, Nokia Shanghai Bell |
| R3-200299 | NGAP Rapporteur corrections | Nokia, Nokia Shanghai Bell |
| R3-200352 | Rapporteur updating of specification 38.401 | NEC |
| R3-200380 | Rapporteur: Editorial updates | Huawei |
| R3-200381 | Rapporteur: Editorial updates | Huawei |
| R3-200562 | TS37.340 Rel-16 Rapporteur Cleanups | ZTE |
| R3-200638 | Rapporteur updates on editorial errors | Huawei |
| R3-200650 | Miscellaneous corrections to 37.473 | Huawei, China Unicom, Orange, TIM |
| R3-200651 | Miscellaneous corrections to 37.470 | Huawei, China Unicom, Orange, TIM |
| R3-200652 | Miscellaneous corrections to 37.471 | Huawei, China Unicom, Orange, TIM |
| R3-200709 | Rapporteur's Update for 36.412 | NTT DOCOMO, INC. |
| R3-200733 | Rapporteur's Update for 36.422 | NTT DOCOMO, INC. |
| R3-200734 | Rapporteur's Update for 38.412 | NTT DOCOMO, INC. |
| R3-200735 | Rapporteur's Update for 38.422 | NTT DOCOMO, INC. |
| R3-201000 | Correction of CR0089r4: CLI Support on XnAP | Ericsson |
| R3-201001 | Correction of CR0208 on Xn Setup Message Size Control | Ericsson |
| R3-201002 | Correction of CR1418 on X2 Setup Message Size Control | Ericsson |
| R3-201030 | Rapporteur Corrections Rel-16 | Ericsson |
| R3-201032 | Rapporteur Corrections Rel-16 | Ericsson |
| R3-201041 | E1AP correction of F1 Support for IPsec Setup | Ericsson |
| R3-201042 | Rapporteur's corrections for TS 38.463 | Ericsson |
| R3-201043 | Rapporteur's editorial corrections for TS 38.463 | Ericsson |
| R3-201207 | Summary of offline discussion for CB: # 1_Email001-Rel-16_rapp_corr | InterDigital |
| R3-201267 | Rapporteur: Editorial updates | Huawei |
| R3-201285 | Miscellaneous corrections to 37.473 | Huawei, China Unicom, Orange, TIM |
| R3-201349 | Correction of CR0089r4: CLI Support on XnAP | Ericsson |
| R3-201427 | Miscellaneous corrections to 37.473 | Huawei, China Unicom, Orange, TIM |
| R3-201487 | NGAP Rapporteur corrections | Nokia, Nokia Shanghai Bell |
| R3-201488 | Rapporteur Corrections Rel-16 | Ericsson |